Server migration

1. Log in on the old server Backup of the database (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 (not an older version). See also section Migration with Update.
3. Make a approval of 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 Vertec.mld translation file, if you are using custom terms or translations.
   • The Userdict.txt and UserLng.txt files, if available.
   • The entire template directory.
   • The entire document directory.
   • At most bat files for automatic backup.
   • If you have custom extensions, the corresponding extensions.
   • If you have a custom web capture, the webkunde folder.
5. On the new server, make the following adjustments:
   • The Vertec directory on the new server should be shared the same as on the old server. This should not require a client setup. The same applies to the templates and documents directories.
   • Vertec.ini check: are the paths correct? Is the name of the database correct?
   • Now make a Restore of the backup created above (or as described in the MS SQL Server article) 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.
   • At most, adjust the bat-file for the automatic backup and set up a scheduled task again.
   • 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 the Vertec.Desktop.App, also the Cloud Servers .
6. If the old server remains on the network after the migration, it is necessary to make sure that no one can continue working with the old database. This can be done simply by renaming the file Vertec.ini on the old server in the Vertec installation directory. If someone tries to start the old installation, they will receive an error message.

If files are copied from one server to another (for example, during a server or program migration), the creation and modification dates are lost.

Among other things, this results in the Vertec showing the date of migration as the creation date for these documents, which means that all of a sudden all documents are from the same date.

To prevent this, there are special tools that can be used to copy the files without losing any 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).

Please note that, depending on the size of the company and the duration of use, a large number of documents may be available. Since copying large amounts of data can take a relatively long time, this should be clarified sufficiently early. At most, it makes sense to copy the files to the new system in advance, so that only the newly created documents need to be copied on the day of the productive migration.

It is quite possible to combine the migration with an update.

With Firebird, this is very easy. Follow the same steps as above. The first time you start Vertec, the database will be converted.

With an MS SQL server you also proceed the same as above, but additionally perform the conversion on the new server according to the article Database Convert .