Part 1 - Installation and Configuration on the New Server
-
Download and install the latest Cloud Connector version on your new server.
- If you were using any 3rd-party providers or ODBC configurations, install and configure the necessary drivers.
- In case you configured x86 mode on your installed Cloud Connector, also configure this on the new Cloud Connector installation.
- Check the Layer2 Backend Service Account on the old machine and if it's not the SYSTEM account, configure the same account for the service on the new server.
- Then contact sales@layer2solutions.com to request a new license file with the new server name and correct version (if upgrading from an older version). Your old license will become invalid when the new one is generated.
Note: If you have an active SA or are using the annual subscription of the Personal, Standard or Enterprise version, the updated license is cost-free.
- Install the new license file per the instructions provided by Sales or refer to the section Installing a License in the user documentation.
Part 2 - Migrating Connections
- Ensure that the connections cannot run in parallel (on old and new server) at any time. Easiest is to completely stop and disable the Scheduling Service on the old server. Another possibility is to disable scheduling per connection that is moved - especially if you are doing a phased connection-by-connection migration.
- It's recommended to migrate the connections one-by-one.
For each connection migration, you will need to copy 2 files to the new server: the associated connection definition file and the Metabase file. Those can be found in the “Connections” and “Metabase” directories under one of these paths:
- C:\ProgramData\Layer2 Cloud Connector (for Windows Vista or higher)
- C:\Documents and Settings\All Users\Layer2 Cloud Connector
You can also move the log and history files, but those are not mandatory for a successful migration.
- If you had any custom alerts/notifications set up in the Nlog.config file, then that file
will also need to be migrated to the Logs folder on the new server to preserve your settings.
- In case you changed the account the Layer2 Cloud Connector Service runs with, please also set this account for the backend service on the new server.
Part 3 - Validating the Connections
In case of a connection-by-connection migration, this last step is executed after each single connection migration.
Go through and make sure that all your connections are still working as intended by launching a manual synchronization run for each migrated connection (or the current migrated one in case of a one-by-one migration).
Once this has been completed, then you can enable scheduling/start the Layer2 Cloud Connector Service to have the jobs run automatically (if appropriate).
After performing all three parts, your migration is done. If you encounter issues along the way or
errors during the connection validation step, contact support@layer2solutions.com for assistance.
