12.5 Prerequisites for C2C Migration from vCloud to Azure

PlateSpin Migrate supports migration of workloads from VMware vCloud Director to Microsoft Azure.

12.5.1 Deployment for C2C Migration from vCloud to Azure

For migration of workloads from VMware vCloud Director to Microsoft Azure, deploy a PlateSpin Migrate server on premise in your source network. With an on-premise Migrate server, site-to-site VPN gateways are required between the data center and Azure and between the data center and vCloud. Figure 12-6 shows the location of various components in your Azure, vCloud, and data center migration environments and the communications between them.

Figure 12-6 Migrate Server on Premise for Migration from vCloud to Azure

You can alternatively deploy the PlateSpin Migrate server from the Azure Marketplace in the target Azure environment. No VPN is required. You use Migrate Agent to register workloads with the cloud-based Migrate server using secure communications over the public Internet. Use data encryption to secure data for replications over the public Internet. Internet access and public IP addresses are required. Figure 12-7 shows the location of various components in your Azure, vCloud, and data center migration environments and the communications between them.

NOTE:A reboot of the source Windows workload is required when you install, uninstall, or upgrade block-based transfer drivers. A reboot is not required for source Linux workloads.

Figure 12-7 Migrate Server in Azure for Migration from vCloud to Azure with No VPNs

12.5.2 Requirements for Migrating Workloads to Azure

To prepare your target Azure environment, review the following information in Section 9.2, Requirements for Migrating Workloads to Azure:

Ensure that the source workload is supported by the target Azure configuration.

12.5.3 Requirements for Migrating Workloads from vCloud to Azure

To use an on-premise Migrate server for migration of workloads from vCloud to Azure:

Deploy a site-to-site VPN between your data center and your Azure environment.
Deploy a site-to-site VPN between your data center and your VMware vCloud Virtual Private Cloud.
Because you are using a VPN Gateway between the data center and Azure, you can use a private IP address for the Migrate server.
Migrate Agent is not required because a VPN is available, but it would also work. For network ports and firewall requirements for registration, see Section 2.6.2, Requirements for Workload Registration.
(Migrate Discovery) Ensure that your source and target network meet the following requirements. See also Figure 12-6, Migrate Server on Premise for Migration from vCloud to Azure.
- Section 2.6.1, Requirements for Discovery.
- Section 2.6.3, Requirements for Migration.

To use a cloud-based Migrate server for migration of workloads from vCloud to Azure without a VPN:

Deploy a PlateSpin Migrate server in the target Azure network environment. Ensure that your non-VPN migration environment meets the Requirements for C2C Non-VPN Migrations.
Azure automatically adds the Remote Desktop Protocol (RDP) port (TCP/3389) and Secure Shell (SSH) port (TCP/22) in the Azure Security Group for the source workload VMs. You must manually add other ports to the source workload’s Azure Security Group that are required by PlateSpin Migrate to provide migration services, such as Port 3725 for replication traffic and Port 443 for HTTPS traffic.
For information about workload login requirements for migration, see the Windows and Linux source workload login requirements in Table 19-2, Guidelines for Machine Type and Credentials for Source Workloads.

12.5.4 Checklist for Automated Migration from vCloud to Azure

Task	Description
Prepare your network resources.	Figure 12-6, Migrate Server on Premise for Migration from vCloud to Azure Figure 12-7, Migrate Server in Azure for Migration from vCloud to Azure with No VPNs Deployment for C2C Migration from vCloud to Azure
Prepare your vCloud migration environment.	Requirements for Migrating Workloads to Azure
Prepare your Azure source workloads for PlateSpin Migrate.	Requirements for Migrating Workloads from vCloud to Azure
Discover target cloud platform.	Section 18.4.2, Target Discovery in the Web Interface
Discover source workloads in vCloud. You can optionally register source workloads with the cloud-based Migrate server in Azure using Migrate Agent.	Section 19.6.2, Workload Discovery in the Migrate Web Interface -OR- Section 19.7, Registering Workloads and Discovering Details with Migrate Agent
Configure target workload migration.	Section 28.2, Configuring Migration of a Workload to VMware vCloud Director
Execute migration.	Section 34.0, Executing Workload Migrations