A company is planning to migrate its on-premises VMware vSphere virtual machines (VMs) to VMware Cloud on AWS. The migration strategy requires that workloads be moved with minimal downtime and that the VMs retain their existing IP addresses during and after the migration. Which TWO steps must the solutions architect take to meet these requirements?
- Deploy the VMware HCX Connector in the on-premises environment and establish a site pairing with the VMware HCX Cloud Manager in the VMware Cloud on AWS Software-Defined Data Center (SDDC).Answer
- Configure an HCX Network Extension to stretch the on-premises Layer 2 networks to the VMware Cloud on AWS SDDC.Answer
- CConfigure AWS Transit Gateway to natively route Layer 2 broadcast traffic between the on-premises vSphere cluster and the VMware Cloud on AWS SDDC.
- DInstall the AWS Application Migration Service (MGN) replication agent on all virtual machines and configure them to replicate data over a public connection with TCP port 1500 blocked for security.
- EConfigure a Pilot Light disaster recovery pattern using AWS Backup to replicate VM storage snapshots every 24 hours to meet a near-zero RTO migration objective.
Answer
To meet the requirements, the solutions architect must deploy the VMware HCX Connector on-premises to pair with the VMware HCX Cloud Manager in the VMware Cloud on AWS SDDC, and configure an HCX Network Extension to stretch the Layer 2 network.
To migrate VMs to VMware Cloud on AWS with minimal downtime while retaining their IP configurations, the solutions architect must set up site pairing between the on-premises VMware HCX Connector and the VMware HCX Cloud Manager. Stretching the Layer 2 network via HCX Network Extension ensures that VMs do not need to be reconfigured with new IP addresses upon cutover.
Step-by-Step Solution
Key Concept
Establishing VMware HCX site pairing and extending Layer 2 networks to allow low-downtime migrations without IP changes.
Estimated Time:2m 0s