DR and Migration

About DR and Migration #

The DR and Migration validated solution provides detailed design, implementation, configuration, and operation guidance on … A VMware validated solution is a technical validated implementation that is built and tested by VMware and VMware cloud providers to help customers resolve common business use cases. VMware validated solutions are cost-effective, performant, reliable, and secure. Each solution contains a detailed design, implementation, and operational guidance.

Automation for This Design in VMware Cloud Foundation #

The implementation tasks for some design decisions are automated by SDDC Manager. You must perform the implementation manually for the rest of the design decisions as noted in the design implication. To provide a fast and efficient path to automating the DR and Migration implementation, this document provides Microsoft PowerShell cmdlets as code-based alternatives to completing certain procedures in each SDDC component’s user interface. You can directly reuse the PowerShell commands by replacing the provided sample values with values from your VMware Cloud Foundation Planning and Preparation Workbook.

Intended Audience #

The DR and Migration documentation is intended for cloud provider architects and administrators who are familiar with and want to use VMware software and a {VVS for CP topic} for VMware Cloud Foundation.

Support Matrix #

The DR and Migration validated solution is compatible with certain versions of the VMware products that are used for implementing the solution.

Software Components in DR and Migration #
VMware Cloud Foundation Version Product Group Component Versions
4.4.1 Products part of VMware Cloud Foundation See VMware Cloud Foundation 4.4.1 Release Notes.
Solution-added products
  • Product One 2.2.x
  • Product Two 3.4.x
4.4.0 Products part of VMware Cloud Foundation See VMware Cloud Foundation 4.4 Release Notes.
Solution-added products
  • Product One 2.0.x
  • Product Two 3.3.x
4.3.1 Products part of VMware Cloud Foundation See VMware Cloud Foundation 4.3.1 Release Notes.
Solution-added products
  • Product One 1.1.x
  • Product Two 3.2.x
4.3.0 Products part of VMware Cloud Foundation See VMware Cloud Foundation 4.3 Release Notes.
Solution-added products
  • Product One 1.0.x
  • Product Two 3.1.x

Before You Apply This Guidance #

To design and implement the DR and Migration validated solution, your environment must have a certain configuration.

Supported VMware Cloud Foundation Deployment #
Workload Domain Deployment Details
Management domain
  • Automated deployment using VMware Cloud Builder.
  • Availability of overlay-backed or VLAN-backed NSX segments in NSX-T Data Center for traffic in the same VMware Cloud Foundation instance and between VMware Cloud Foundation instances not required.

See the following VMware Cloud Foundation Documentation:
  • For information on deploying the management domain, see VMware Cloud Foundation Getting Started Guide and VMware Cloud Foundation Deployment Guide.
  • For information on designing the management domain, see VMware Cloud Foundation Design Guide for the Management Domain.
(Optional) One or more virtual infrastructure workload domains
  • Automated deployment using VMware Cloud Builder.

See the following VMware Cloud Foundation Documentation:
  • For information on deploying the management domain, see VMware Cloud Foundation Getting Started Guide and VMware Cloud Foundation Deployment Guide.
  • For information on designing the management domain, see VMware Cloud Foundation Design Guide for the Management Domain.

Overview of DR and Migration #

By applying the DR and Migration validated solution, you implement {describe outcome}.

Implementation Overview of DR and Migration #
Stage Steps
1. Stage one description Long form description of stage
2. Stage two description
  1. Step 1 description
  2. Step 2 description
  3. Step 3 description
  4. Step 4 description
3. Stage three description
  1. Step 1 description
  2. Step 2 description
  3. Step 3 description

Update History #

This DR and Migration solution is updated when necessary.

Revision Description
1. 31 MAY 2022 Long form description of revision
2. 28 APR 2022
  1. Revision 1 description
  2. Revision 2 description
  3. Revision 3 description
  4. Revision 4 description
3. 29 MAR 2022
  1. Revision 1 description
  2. Revision 2 description
  3. Revision 3 description

Introduction #

Welcome! Here you can find suggestions on how to plan, set up and operate your DR and Migration services.

VMware Cloud Director Availability #

VMware Cloud Director Availability is a Disaster-Recovery-as-a-Service solution. It is specially designed and available for participants in VMware Cloud Provider Program and allows them to protect and migrate vApps and VMs:

  • From on-premises vCenter Server site to a VMware Cloud Director cloud
  • From VMware Cloud Director cloud to an on-premises vCenter Server environment
  • Between VMware Cloud Director managed clouds

Use Cases #

VMware Cloud Director Availability supports two different use cases – disaster recovery and migration of vApps/VMs. Both of them rely on replication of virtual machines. In both cases at least one of the sides is a VMware Cloud Director managed cloud and the other side could be another VMware Cloud Director cloud or vCenter on-premises site. VMware Cloud Director Availability cannot protect or migrate bare metal servers or VMs managed by non-VMware hypervisors.

VMware Cloud Director Availability Use Cases

Disaster Recovery #

A tenant can purchase DRaaS provided by a public cloud and based on VMware Cloud Director Availability to protect their virtual machines running in their on-premises datacenter. The Cloud Provider assigns a portion of compute, storage, and network resources from their cloud and groups them in an Organization Virtual Data Center (OrgVDC) that belongs to the tenant. Also, the Cloud Provider can enable this OrgVDC (respectively, the tenant) to protect their on-premises virtual workloads to the cloud with specific parameters like minimum RPO, bandwidth control, direction of the protection, and more. It allows the tenant to failover their VMs in case of an outage in their on-premises data center.

Migration #

When tenants plan to migrate workloads to the cloud, they may use the Migration workflow to simplify the process. When a “New Migration” is configured, VMware Cloud Director Availability starts replication of the vApp/VM from the source to the destination.

Appliances #

There are three VMware Cloud Director Availability appliances required for the setup in the cloud and one on-premises appliance to be deployed at the tenant’s on-premises site.

Cloud Replication Management Appliance #

The Cloud Replication Management appliance is responsible for the communication with VMware Cloud Director. Based on this communication, it discovers resources (OrgVCD, storage policies, datastores, networks, etc.) managed by VMware Cloud Director and used by the tenants. This information is required for discovering vApps/VMs that can be replicated/migrated or suitable destination locations for incoming replications/migrations.

It also provides the VMware Cloud Director Availability UI and API interfaces. Another role of this appliance is to communicate with all the local and remote Replicators and receive data regarding each protected/migrated workload. Two VMware Cloud Director Availability services cover these functionalities in Cloud Replication Management appliance – the cloud.service and the manager.service.

Cloud Service #

This service understands the VMware Cloud Director constructs – OrgVCD, vApps, networks managed by VMware Cloud Director, storage policies, etc. To achieve this VMware Cloud Director Availability Cloud Management appliance communicates with the VMware Cloud Director API through the VMware Cloud Director LB. The Cloud Replication Management appliance does not communicate with the VMware Cloud Director consoleproxy cells/interfaces. Based on this, VMware Cloud Director Availability can:

  • discover VMware Cloud Director managed vApps/VMs and protect/migrate them to another DR-enabled cloud or on-premises vCenter
  • discover a suitable destination for incoming replications/migrations

The cloud service manages pairings with other DR-enabled clouds, policies, SLA profiles, and their assignment to VMware Cloud Director organizations. It provides information about the replication and system tasks. Also, it reports the replication compute resources consumption per tenant and per PVDC, the storage consumption per datastore, plus many other high- and low-level details. The cloud service management interface is available on https://vcda_manager_fqdn:443/admin. It is possible to log in with the local OS root account, an SSO account if the appliance has registration in an SSO domain, or with a VMware Cloud Director System Administrator account if the initial configuration is already completed.

Manager Service #

The manager service manages the registrations of local and remote replicators. During the pairing process, remote replicators are registered in the Cloud Replication Management appliance. For each replication, it chooses one replicator from the source site and one from the destination site. The destination replicator is responsible for discovering the appropriate resources to create the replica disks at the destination and write data. Replicators send information to the Cloud Replication Management appliance about their operation – statuses, amount of data replicated, operation start time, time to complete, etc. The manager service is also used to manage replicators. It can trigger the rebalancing of replications across all replicators or put a replicator in maintenance mode, which leads to assigning each of its replications to another one. This is useful when the current replicators need to be offloaded by adding a new replicator in the solution.

The manager service management interface is available at https://vcda_manager_fqdn:8441. It is possible to log in with the local OS root account and an SSO account if the appliance is already registered in Lookup Service.

Cloud Replicator #

Cloud Replicator is responsible for moving the replication data around - to and from the ESXi hosts and the cloud. For outgoing replications/migrations, it communicates with the VMKernel interface of the ESXi host, captures and encrypts replication data, optionally compresses it, and sends it to the remote replicator, which can be another Cloud Replicator or on-premises Replicator. For incoming replications/migrations the Cloud Replicator receives replication data from a Replicator (cloud or on-premises), decompresses and decrypts this data, and sends it to the ESXi to be written on a datastore. Cloud Replicator is the only component that can scale out as the number of protections/migrations increases.

Cloud Tunnel #

The Cloud Tunnel appliance is the single-entry point to the VMware Cloud Director Availability instance in the cloud. Its role is to handle and forward the incoming management and replication traffic. It is the only VMware Cloud Director Availability appliance that needs a dedicated Internet-accessible endpoint.

On-premises Appliance #

The VMware Cloud Director Availability on-premises appliance is deployed in the tenant data center. It creates a pairing relation to VMware Cloud Director Availability in the cloud and can protect and/or migrate VMs running locally. The on-premises appliance does not require a public endpoint as it only initiates connectivity to the cloud. A single on-premises appliance can protect VMs from a single SSO domain even if there are multiple vCenter Servers in this SSO domain. If the requirement is to do replications from the cloud to on-premises, then a single appliance is required for each vCenter due to how placement works. Also, one on-premises appliance can be paired to a single VMware Cloud Director Availability instance in the cloud. If the tenant intends to use more than one DR service in the cloud, a dedicated appliance is required for each cloud DR service.

Reference #

Official documentation