Running SQL Server or Redis on an Independent Server

Normally, you should use the default SQL Server Express Instance that is installed with CloudM Migrate when installing a primary service. Using an existing SQL Server Instance should only be done in specialised scenarios or when installing a secondary service.
If you are using a standalone SQL environment and intend to introduce a new primary server, it is essential to create a new SQL instance to establish a connection. You can export the configurations from your current primary server and import them to the new primary server. However, please note that the migration history cannot be preserved.

When you are installing secondary services you should also use an existing SQL Server Instance, but please follow the instructions for setting up a secondary server.

If using a full SQL instance it is recommended that it is run on the CloudM Migrate Primary server to maintain performance. Ensure that the primary server meets or exceeds all of the system requirements.

Custom Redis Setup

By default, CloudM Migrate uses a Redis server on the same server as the SQL Server instance.  If a non default SQL Server instance is used then some custom configuration for Redis is required.  It is also possible to use Redis on a completely independent server, where custom configuration is also required.

'Redis Server Location' should be set in the CloudM Migrate Service Manager to the IP address or hostname of the Redis server instance. If this is not set Redis will not be able to communicate with SQL and migration will fail.  Make sure that the internal IP address of the Redis server is specified.  This setting only needs to be applied to the primary server.


Was this article helpful?
0 out of 1 found this helpful