1. First page
  2. Documentation
  3. Administration Manual
  4. System Maintenance
  5. Backup and restore
  6. System migration

System migration

Instructions for correctly migrating EBA DMS to a new server.

Notes: Below notes are written only as recommendations. Full instructions eg. migration process can not be written because each client has slightly different layout and settings and is impossible to replicate each environment. It is recommended that you first perform the migration for the test.

Always migrate to the same EBA DMS verison! Do not migrate to lesser or greater version! If you do not have installers of your version then upgrade your system first and make sure it works fine.


All users should save and finish the work and close the EBA DMS client. Check in EBA DMS System whether there are any logged in users and log them out.

Make the database inaccessible to all users before starting work, only allow access from the computer on which the work will be performed (usually server). Another option is to temporarily rename the .ini file so that the database connection to the program will not be possible.

Checklist before executing migration procedure:

  1. Which DB type you use?
    1. Check DB type. If you are moving to another DB type, please check if all necessary settings were set – prerequisites for MS SQL, Oracle.
  2. Which EBA DMS version do you use?
    1. Check if you have installers for both EBA DMS Client and Application Services.
    2. Check if you use 32 or 64bit EBA DMS Clients.
    3. Oracle: Make sure you have oracle drivers (oci.dll). You must install them for each EBA DMS Client installation – see here. Make sure if you need x64 or x86 drivers. Check also if you need drivers for Oracle 11 or 12.
  3. Scripts and integrations
    1. Check if you have any projects or plugins installed.
    2. Check if you have any integrations with other Software.
    3. Check if you have COM integration with other Software. Make sure to run /regserver option if needed.

Migration procedure:

  1. Make old (existing) database unaccessible to other users except you.
  2. Make a full backup of the database. You can use SQL Browser tool.
  3. Install a database on the new server. Make database user. Perform a basic database configuration. If you are using MS SQL database, make sure you followed following instructions while creating new database: Setting up MS SQL database
  4. Install the EBA DMS (Client, Application Services, and EBA printer if needed) on the new server.
    You must install the same version as you had on the old server.
  5. Restore the database backup on the new server. You can again use SQL browser tool.
  6. Leave the database on the old server inaccessible so that no one will connect to the old database.
  7. Back up EBA DMS folders, EBAAutomaion_ [name], EBA_share folders, or keep the old server fully accessible until you fully validate system on the new server.
  8. Copy configuration files. Copy .ini configuration for EBA DMS clients from the old server. Copy .ini configuration files from EBA_Automation folder into new EBA_Automation installation.
  9. Check all database connections. Check all entries in .ini file, check entries in ControlCenter and check entries for external database (if you have changed server IP for example).
  10. Recreate FTS index. Run ebaautomation4.exe with following parameter: -recreatesearchindex
    Executing the command can cause heavy load on a database. Execute in after hours.

How can we help?