Server migration

1. Make a Backup of the database on the old server (for MS SQL Server make a backup of the database as usual).
2. Reinstall Vertec on the new server. Use at least the Vertec version that was running on the old server (no older version). See also Migration with Update.
3. Share the new Vertec directory (the clients need at least read access to Vertec.Desktop.exe or Vertec.Cloud.exe).
4. The following files must be applied:
   • The backup of the database created under point 1, in the case of Firebird Vertec.fbk.
   • The entire document directory, if you have set the Document Storage to Dateisystem oder DMS in the Vertec system settings. See also the section Copy document tray.
5. Make the following adjustments on the new server:
   • The Vertec directory on the new server should be shared in the same way as on the old server. This should not require any client setup. The same goes for the document directory if you need to apply it (see point 4).
   • Vertec.ini check: are the paths correct? Is the database name correct?
   • Restore the backup created above (or as described in the article Ms sql server) as an active database.
   • Open Vertec and adjust the Document Path if necessary.
   • Make sure that the users have the same user rights on the new document directory as before.
   • Set up regular backup of the new database.
   • Make sure that port 3050 (TCP) is open for Firebird.
   • Make sure that the Notif port (see Notif section in Vertec.ini) is open. When using Vertec.Desktop.app, also the Cloud Servers port.
6. If the old server remains on the network after the migration, make sure that no one can continue to work with the old database. This can be done by renaming the Vertec.ini file on the old server in the Vertec installation directory. If someone tries to start the old installation, they will receive an error message.

When files are copied from one server to another, the creation and modification dates are lost.

This leads, among other things, to Vertec showing the migration date as the creation date for these documents, which means that all of a sudden all documents are of the same date.

To prevent this, there are special tools that can be used to copy the files without losing the dates. An example of such a tool is PureSync, which can be found at https://www.jumpingbytes.com/puresync.html (Please note that this is a product that Vertec has nothing to do with and therefore Vertec disclaims any liability for the use of this product).

It is possible to combine the migration with an update by installing the latest version on the new server, making sure that you do not skip more than one database version, see Update vertec on-premise.

Otherwise, proceed as described above. With Firebird, the database will be converted the first time Vertec is started.

For MS SQL Server, you also do the same as above, but additionally perform the conversion on the new server according to the article Database Convert.