Migration of current projects to a new machine

We are currently planning to migrate our Visual Paradigm environment.
Our current installation is version 16.2, running on Windows Server 2012 with SQL Server as the database engine.

The target environment will be version 17.2, running on Windows Server 2019 with SQL Server 2019.

We kindly request your guidance on the recommended procedure for performing this migration, as we have encountered issues during the process, particularly with the migration and configuration of the database on the target server.

Thank you for your inquiry. Basically you can follow the procedure below to migrate your server:

One thing you need to understand is the core of migration process is pack up your existing server, and restore to a fresh environment, including the DB. It cannot restore to an existing DB.

Below is the summary of the procedures:

  1. Make a full backup to your v16.2 environment (server, DB, repository folder (if configured not inside VP Server installation directory) etc…)

  2. Download and unpack the v17.2 server side-by-side to your v16.2 server

  3. Execute the migration.sh from the v17.2 server, with target as the v16.2 server. This will pack up your v16.2 server into “VPServerExport” folder inside scripts folder of your v17.2 server.

  4. Setup a new DB in your SQL Server, make sure user account is correctly configured and allow JDBC connection from your “new server”.

  5. Unpack another v17.2 server to the installation location in your “new server”.

  6. Copy the VPServerExport generated in step 3 to the WEB-INF folder of the v17.2 VP Server on your “new server”

  7. Startup the v17.2 VP Server on your “new server”

  8. Follow the on-screen wizard to perform migration. On the DB setup step specify the connection to the new DB created in step 4.

Once completed all data will be restored to the new server with connection to the new DB. If there are any further inquiry, please do not hesitate to contact me.