VMware Hybrid Cloud migrations

After the VMware HCX™ Service Mesh and Network Extensions are provisioned and extended, the next step is the migration of virtual machines (VMs).

The following migration types exist:

vMotion
Bulk Migration
Cold Migration

Operation

Use the HCX web UI snap-in portal or the vSphere Web Client contextual extension menus to initiate a cross cloud vMotion. In either case, the same migration wizard comes up. For the contextual menus, only a single VM is selected for migration operations. For the portal, multiple VMs can be selected.

Reverse migrating VMs is only possible from the web UI portal that uses the Reverse migration checkbox in the HCX Migration wizard.

vMotion

The vMotion capability within HCX extends the vSphere vMotion capability to work across differing versions of vSphere, separate SSO domains, and various types of network connectivity across the internet. HCX assumes that the network used to connect across is not secure and it always moves traffic through encrypted tunnels regardless of the type of connectivity.

Concepts and best practices for vMotion

HCX is essentially a vMotion two-way proxy. Each instance of HCX emulates a single VMware ESXi™ host within the vSphere data center, outside any clusters. The HCX instance is a “front” for the cloud gateway fleet component (CGW). A proxy host appears for each HCX site that is linked to the currently viewed site. When a vMotion is initiated to a remote host, the local ESXi host migrates that VM to the local proxy ESXi host.

A vMotion migration is initiated from the remote ESXi proxy host to the destination vSphere physical ESXi host, while it receives data from the source CGW across the tunnel. When vMotion is employed, unlike the bulk migration option, only a single VM migration operation runs at a time. As a result, for many VMs to be migrated, it is recommended to use vMotion only when downtime is not an option or if a risk in rebooting the VM exists. However, like standard vMotion, the VM can be live during the process.

A single vMotion will top out at around 1.7 Gbps on the LAN and 300 - 400 Mbps on the WAN through the WAN Optimizer. This does not mean that 1.7 Gbps on the LAN equals to 400 Mbps on the WAN through the WAN Optimizer, but rather that these maximums were observed on specific environments. Such an environment consisted of 10 GB LAN vMotion Network and 1 GB internet uplink, which is shared with production web traffic.

Use vMotion in the following cases:

If the VM is difficult to shut down, start, or uptime is long and can introduce risk by shutting down the VM.
For any cluster type application that requires disk UUIDs, such as Oracle RAC clusters. vMotion does not change the disk UUIDs on the destination.
If you want to move a single VM as quickly as possible.
If scheduled migration is not required.

Bulk migration

Concepts and best practices for bulk migration

The bulk migration capability of HCX uses vSphere replication to migrate disk data while re-creating the VM on the destination vSphere HCX instance. A migration of a VM incurs the following workflow:

Creation of a new VM on the destination side and its corresponding virtual disks.
Replication of VM data to the new VM. Replication starts as soon as the wizard is completed regardless of switch over scheduling.
Power down of the original VM.
During the power off period, final replication of any data changes occurs.
Powering on the new VM on the destination side.
Rename and move of the original VM to the cloud folder to which it was moved.

The following are advantages of bulk migration over vMotion:

Migration of multiple VMs concurrently.
More consistent bandwidth use. vMotion can generate fluctuations in bandwidth use that would be visible as peaks and valleys within network monitoring tools or the WAN Opt UI.
Use bulk migration to obtain an overall use of a network bandwidth capability higher than if you use a single vMotion.
Schedule bulk migration to switch to the newly migrated VMs during a scheduled outage window.
Allow migration of VMs that are currently using virtual CPU features, which differ from the cloud side. vMotion migration might fail in these cases.

The following are disadvantages of bulk migration over vMotion:

Individual VMs migrate much more slowly than with vMotion.
The VM incurs downtime briefly as the new clone VM is brought up on the destination side.
VMs that depend on disk ordering and disk UUIDs (Oracle RAC) can have issues and have disks that show up differently as the UUIDs are changed, which might change the OS paths to the virtual disk devices.

Migration type best practices

Shared disk clusters

Oracle RAC, MS Exchange, and MS-SQL clusters are examples of applications where two or more VMs participate in a cluster that requires shared disk across all VMs or cluster nodes. The VMware® multi-writer flag needs to be enabled on all of the VM nodes for disks that are part of the application cluster (non-OS virtual disks). VMs with the multi-writer flag enabled for any virtual disk are not supported.

Review the following information about migrating a multi-writer virtual disk enabled cluster:

vMotion is used, as the original VM disk and UUID mappings are maintained.
The cluster remains up in a degraded state (single node) during migration.
The cluster incurs downtime before the start of the migration and after the migration is complete to reassemble the multi-writer configuration across cluster VMs.

To migrate a multi-writer disk enabled cluster, complete the following steps:

Power off the cluster and all nodes per the application best practice.
Take note of the disk order, if the application requires it, in each node VM for the multi-writer configured virtual disks.
For Oracle and any other application that uses the virtual disk UUID feature, log in to an ESXi host and run the command vmkfstools -J getuuid /vmfs/volumes/datastore/VM/vm.vmdk. This command gets the UUID of each virtual disk file that requires the multi-writer flag set for the cluster. This step is necessary if best practice aligns disk orders with how the path is displayed in the operating system. vMotion can reorder the disks (disk1, disk2, disk3) but the UUIDs remain the same. When the migration is complete, use the noted UUID to map the disk information to re-create the disk naming order and the SCSI ID if necessary. This information can be useful for troubleshooting when an Oracle instance has many virtual disks that are mapped.
Remove the virtual disks from all cluster VMs except the one deemed primary.
Remove the multi writer-flag from the primary cluster VM (the only one that owns the cluster disks).
Power on the primary cluster, if required for minimal downtime.
Migrate all cluster nodes with vMotion. Migrate the primary cluster first. Migrate all other nodes after they are powered off.
When the primary disk owning node completes migration, power it off.
If required, remap the disk order with the proper disk UUID and scsi ID. Remapping is not required for the application to function.
Re-enable the multi-writer flag on the primary node.
Start the primary node and verify operation.
Map disk or enable multi-writer flag on all other cluster VMs and power them on.
Verify other cluster operation.

General VMs

After confidence is built around the function of HCX, bulk migration must be employed. Bulk migration is necessary for redundant applications. For example, web servers and where many 100s or 1000s of VMs are to be migrated.

VMs that use direct attached NAS

NFS is typically employed for use to share data across many servers, such as web server content. iSCSI can be employed across VM nodes that consist of an application cluster such as email or RDBMS and is typically more latency sensitive than NFS.

In either case, if latency can be kept low to the IBM Cloud data center (< ~7 ms for iSCSI and whatever the application tolerates for NFS) and allowing that the application can operate with bandwidth of ~1 Gbps or less, then the NAS network can be stretched with HCX into an IBM Cloud location. Afterward, the VMs can be migrated or vMotioned with HCX.

Post migration, iSCSI volumes can be mirrored with the OS to another local cloud storage solution and NFS data can be replicated to any cloud solution. Review the following considerations:

Latency (iSCSI or application tolerance for NFS)
Bandwidth (~1 Gbps per stretched network)
Underlay link bandwidth

After the migration lifecycle, test Development or staging applications before you attempt the migration on production. QoS can be employed for the underlay tunnel traffic (UDP 500/4500) between the L2C HCX appliances that support latency sensitive stretched L2 networks.

Network swing

If the goal is data center evacuation into the IBM Cloud, then the next to last step before HCX removal is the network swing. Network swing achieves a migration of the network subnet that houses the migrated VMs from the source data center to a VMware NSX® overlay network within the IBM Cloud.

Swinging the network involves the following steps:

Verify that the network is evacuated of all workloads and any non-VM networked devices are either moved to another network, functionally migrated to cloud, or deprecated.
Verify any NSX topology or IBM Cloud supporting network topology is completed to support the network swing. For example, dynamic routing protocols and firewalls.
Run an HCX unstretch network workflow in the UI and select the appropriate routing NSX device to take control of the default gateway of the unstretched network.
Run any external routing changes, which can include inserting changed routing for networks that were migrated, removing routes to source site from the migrated network, and ensuring that routing to the migrated subnet across the WAN still works for the applications that were not migrated.
The application owner tests the migrated applications from all possible access points: the Internet, the intranet, and the VPN.

For example, you want to network swing an application that has all VMs migrated to the cloud:

You are using a vyatta on the private network side to insert routes into your MPLS cloud and to tunnel to the edge routing devices on the MPLS so you can avoid the IBM Cloud IP space.
You have your account set with an IBM Cloud VRF.
Some applications are behind a network load balanced virtual IP (vIP). Those vIPs are on your owned subnet that's located on a virtual F5 behind the vyatta.

Adding more specific routing into the MPLS for networks that are swung over to IBM Cloud through HCX works fine for other networks. However, it does not work for the individual vIPs because a /32 route is being added.

The common solution for WAN providers is to filter out /32 routes that are added. Work with the WAN vendor to allow.

The following are considerations and implications:

Applications that share subnet, vLAN, and VXLAN need to move together.
Applications behind a load balancer that uses an internal routable IP can require routing changes if they cannot be moved together or it is not desirable to do so. For example, involving too many applications in one swing can be perceived too much of a risk.
VMware admins, network admins (including customers and WAN vendors), and application owners need to be involved, even if there's no planned impact on a particular system or network equipment.