The following instructions explain how to set up servers using Virtual Machines set up in Google Cloud Platform (GCP). For more information, see here.
There are several other methods that you can use to set up your servers, including using Microsoft Azure (Windows Azure).
CloudM recommends setting up Virtual Machines using Google Cloud Platform when migrating to Google (and Microsoft Azure when migrating to Microsoft) to limit network traffic costs.
All CloudM Migrate secondary servers must be on the same VM network as the primary server. The default network configuration for new VM instances in GCP does not need to be modified to meet this requirement.
You will also need a GCP billing account and associated GCP project for creating VM instances and to be mindful of the associated costs.
The instructions differ at various points throughout this guide depending on the type of server being created and configured (primary or secondary), and these steps are highlighted in bold.
Creating a VM instance
- Access the Google Cloud Platform console
- Open the Google Cloud Platform project to be used for the CloudM Migrate server/s, using the dropdown icon at the top of the screen.
- Navigate to Compute Engine > VM instances
- Select CREATE INSTANCE
- Enter a name for the VM instance.
- Keep the name to less than 15 characters to avoid connection issues in multi-server environments. See Resource naming conventions.
- Standardize the naming convention for all instances, using numbering (1,2,3) or lettering (a,b,c) to help you differentiate between instances.
- Select the ‘Machine Type’ dropdown menu and then, select ‘Custom’
- In larger migrations, where numerous secondary servers will be utilized, you should change the Virtual Memory of the Primary VM from the default Custom, which has a low threshold, to 'System Managed'. This is to improve performance of the Primary Server as it communicates with the REDIS database.
- Alternatively, select e2-standard-4 (4 vCPUs, 16 GB memory) as the Machine Type for a Primary Server and e2-standard-2 (2 vCPUs, 8 GB memory) for any Secondary Servers. These settings should be able to accommodate most migrations without spiralling cost.
- Change the number of cores and memory to meet the CloudM Migrate system requirements (note the different requirements for primary and secondary servers.
- Select ‘Change’ in the ‘Boot disk’ section:
- On the Public Images tab, change the:
- ‘Operating system’ to ‘Windows Server’.
- ‘Version’ to ‘Windows Server 2019 Datacenter’ (or another supported version of your choice).
- ‘Size (GB)’ to ‘300’ (the combined minimum requirements for both CloudM Migrate and Windows Server).
- Select Create to create the VM instance.
Connecting to a VM instance
- Go to the VM instances screen. Under the Connect column, select the small down arrow and then Set Windows password:
- Leave the Username field as the default, and then select SET:
- Copy the password and make a note of it for later:
- Under the Connect column, select the small down arrow and then Download the RDP file:
- Using the RDP (Remote Desktop Protocol) file, establish a connection and login to the VM instance using the password noted down earlier:
- If it fails to connect, disable your local environment Windows firewall and any other network firewalls.
Cloning a Virtual Machine
Cloning an existing Virtual Machine is a great way to create as many Secondary VM's as you need really quickly, without needing to go through the entire process each time. It also makes sure that all Virtual Machines have the same specifications (unless you want to make changes) and avoids human error.
To clone an existing Virtual Machine:
- Login to Google Cloud Platform and go to Compute Engine > VM instances,
- From the list displayed, click on the name of the Virtual Machine that you want to clone,
- On the next screen, click on the Create Similar button at the top of the screen (next to Create Machine Image).
- Edit any specifications that you want to change, if required. You should only need to change the name (so that you can differentiate between your Virtual Machines), but can change other aspects such as Machine Type and Boot Disk options.
- Click Create.
- Your cloned VM will now appear in the list of Virtual Machines on the Compute Engine > VM instances screen.