SQL Express is usually installed on the Primary migration server as part of the default install of CloudM Migrate. However, full SQL Server can be used in its place and hosted on an independent server.
This guide is in addition to the standard installation articles and assumes that the Migration Server (Primary) and SQL Server are hosted as Virtual Machines in Google Cloud Platform (GCP).
Usually, it is simpler to do an In-place upgrade of SQL Express
Primary Migration Server
Setup and configure Windows Server based on the standard CloudM Migrate recommendations, but do not install Migrate yet.
- Disable the Windows Firewall
- Configure MSDTC (dcomcnfg)
- Test with the DTC Ping tool
SQL Database Server
Install Windows Server and then download and follow the defaults to install Microsoft SQL Server and SQL Management Studio
Once installed, open SQL Management Studio and follow the instructions here to create a SQL user with dbcreator and public role
Disable Windows Firewall and configure MSDTC as with the Primary Migration Server.
Firewall
GCP Firewall can be accessed here: https://console.cloud.google.com/networking/firewalls
An Ingress rule/rules should be applied to allow data to flow through the following ports:
1433,5000-5020,1801,6379
- SQL Server = 1433/1434
- Microsoft Distributed Transaction Coordinator = 5000-5020
- MSMQ = 1801
- Redis Server = 6379
Installing CloudM Migrate
Download and Install the latest version of CloudM Migrate. Choose the Advanced option to specify an existing SQL Server.
Select 'Use Existing SQL Server' and populate the following fields.
- Server Name - This will be the server/server sql instance where your database resides. SQL SERVER may not require an instance name if it was installed without one, in which case just specify the server name
- Database - Database name, usually PoweredBy - this and NServiceBus databases will be created by the install process.
- User Name - SQL user that has access to the database entered in the previous step.
- Password - SQL user password
The installer will connect to the SQL Server and create two databases (under the Databases folder in Management Studio) - PoweredBy and NServiceBus. Additional databases will be created as projects and configurations are added.
Once CloudM Migrate has installed on the Primary server, open the CloudM Service Manager and change the Redis Server Location.
An older Windows version of Redis is installed by default to the Primary migration server, but the latest version of Redis can also be installed to its own Linux server. By default the Redis Server Location is blank which means that Migrate thinks Redis is installed alongside the SQL Server. This empty field should be changed to the primary server hostname or the Redis Linux server hostname/IP address.
Troubleshooting
Check that the Ports are open and connect
Install Telnet to test if the ports are open
Run the following command: >cmd > telnet <servername> <port>
- If it connects - Good
- If it fails - Recheck GCP and the Windows firewalls.
Secondary Servers are not connecting
- Go to SQL Server Configuration Manager
- Open SQL Server Network Configuration
- Click on your Named Instance
- Ensure TCP/IP Enabled
- Open TCP/IP
- Click on IP addresses
- Add Port 1433 to all IP's
- Restart MSSQL service
Comments
0 comments
Please sign in to leave a comment.