DR and Migration Planning and Preparation

DR and Migration Planning and Preparation #

Before you start implementing the components of the DR and Migration solution, you must set up an environment that has a specific compute, storage, and network configuration, and that provides external services to the components of the solution.

Use the VMware Cloud Foundation Planning and Preparation Workbook to capture environment specific input values that are required during the implementation.

Carefully review the VMware Cloud Foundation Planning and Preparation Workbook before implementation to avoid costly rework and delays. Capture input values that are specific to your environment and verify that the components that are required by this solution are available.

The VMware Cloud Foundation Planning and Preparation Workbook contains inputs for each implementation and configuration procedure. Reference your values from the VMware Cloud Foundation Planning and Preparation Workbook to complete UI or PowerShell procedures.

#External Services You use services that are external to VMware Cloud Foundation when implementing the solution-name solution.

External Service Description
Active Directory (AD) Active Directory (AD) is used to provide authentication and authorization to the VMware Cloud Foundation infrastructure.
This includes dedicated Domain Users with least privilege access to act as service accounts for component connectivity.
Domain Name Services (DNS) Domain Name Services is used to ensure components are resolvable by FQDN and by IP address.
Network Time Protocol (NTP) Network Time Protocol is used to synchronize time consistently across components.
Certificate Authority (CA) Certificate Authority is used to provide signed certificates for user facing interfaces.

Everything you need to know before deploying VMware Cloud Director Availability.

Hardware Requirements #

Appliance Type Description and Services Hardware Requirements
Cloud Replication Management Appliance A dedicated appliance, that runs the following VMware Cloud Director Availability services: * Manager Service * Cloud Service with embedded VMware Cloud Director Availability Tenant Portal - 2 vCPUs
- 4 GB RAM
- 10 GB Storage
Cloud Replicator Appliance A dedicated appliance for the Replicator Service that handles the replication traffic for a site. For large-scale environments, you can deploy more than one Cloud Replicator Appliance per cloud site. - 4 vCPUs
- 6 GB RAM
- 10 GB Storage
Cloud Tunnel Appliance A dedicated appliance for the Tunnel Service. - 2 vCPUs
- 2 GB RAM
- 10 GB Storage

Other Requirements #

The resource vCenter Server instances within a VMware Cloud Director site must be within the same single sign-on domain. All Replicator Service, Manager Service, Cloud Service, and Tunnel Service instances within the respective site must be configured with that same single sign-on domain.

Network Ports #

Source Destination Port Number Protocol Description
VMware Cloud Director Availability Replicator ESXi Hosts 902 TCP and UDP Used by the VMware Cloud Director Availability Replicator service for replication traffic to the destination ESXi hosts.
VMware Cloud Director Availability Replicator VMware Platform Services Controller® 443 TCP Used for single sign-on and Lookup Service communication.
VMware Cloud Director Availability Replicator vCenter Server 443 TCP Used by the local VMware Cloud Director Availability vApp Replication Manager service or the VMware Cloud Director Availability Replicator service for communication with the local vCenter Server.
VMware Cloud Director Availability Replicator VMware Cloud Director Availability vApp Replication Manager 8044 TCP Used for vCloud Availability vApp Replication Manager management from the vCloud Availability Replicator.
VMware Cloud Director Availability Replicator VMware Cloud Director Availability Tunnel 8048 TCP Used for VMware Cloud Director Availability vApp Replication Manager management from the VMware Cloud Director Availability Replicator.
VMware Cloud Director Availability vApp Replication Manager VMware Platform Services Controller® 443 TCP Used for single sign-on and Lookup Service communication.
VMware Cloud Director Availability vApp Replication Manager VMware Cloud Director service 443 TCP Used for VMware Cloud Director Director management from the VMware Cloud Director Availability vApp Replication Manager. 
VMware Cloud Director Availability vApp Replication Manager VMware Cloud Director Availability Replicator 8043 TCP Used for VMware Cloud Director Availability Replicator management from the VMware Cloud Director Availability vApp Replication Manager. 
VMware Cloud Director Availability vApp Replication Manager VMware Cloud Director Availability Tunnel 8047, 8048 TCP Used for VMware Cloud Director Availability Tunnel management from the VMware Cloud Director Availability vApp Replication Manager. 
VMware Cloud Director Availability Tunnel VMware Cloud Director Availability Replicator 8043, 44045 TCP Used for VMware Cloud Director Availability Replicator management from the VMware Cloud Director Availability Tunnel. 
VMware Cloud Director Availability Tunnel VMware Cloud Director Availability vApp Replication Manager 8044, 8046 TCP Used for VMware Cloud Director Availability vApp Replication Manager service management from the VMware Cloud Director Availability Tunnel appliance. 
VMware Cloud Director Availability Tunnel VMware Platform Services Controller® 443 TCP Used for VMware Platform Services Controller® communication management from the VMware Cloud Director Availability vApp Replication Manager and VMware Cloud Director Availability Replicator. 
ESXi Hosts VMware Cloud Director Availability Replicator 31031, 44045, 44046 TCP Used by the ESXi hosts for replication traffic to the destination VMware Cloud Director Availability Replicator service. 
Firewall VMware Cloud Director Availability Tunnel 8048 TCP Used for redirecting external traffic management to the VMware Cloud Director Availability Tunnel service. 

Important Considerations #

Replication Traffic #

A typical good practice is to separate the management and resource vCenters/clusters. The number of hosts in resource vCenters/clusters is significantly higher than the number in the management cluster. A recommendation is to deploy Replicators on resource hosts and not in the management cluster so more Replicators can be deployed and a DRS rule can be created to keep the Replicator VMs on different hosts for better load distribution. Also, the replication traffic path from the Replicator appliances to the replication network on the resource hosts will be enhanced. The hosts can use the management vmkernel interface to communicate with the Replicator. Another option is to have a dedicated vmkernel interface for replication purposes only. Using the management vmkernel simplifies the configuration but significantly reduces the control options available to the administrator and can lead to a risk for routing uncompressed replication traffic, which is highly non-desired. The general recommendation is to use a dedicated vmkernel for the replication traffic. In this case, the administrator will have better control over the infrastructure. Using NIOC, the administrator will be able to set shares for different types of vmkernel traffic. It enables carrying the replication traffic over dedicated uplinks.

Note: If any other VMware HBR-based replication products (vSphere Replication, VMware Site Recovery Manager or VMware HCX) are used in this cloud, configuring a dedicated vmkernel interface marked with “vSphere Replication” and “vSphere NFC Replication” will lead to all of these products try to use it. This means the network connectivity between their appliances and the replication vmkernel interfaces will be required to enable all of these products to operate successfully. For more information, please consult with respective product documentation.

Storage Requirements #

For a successful test failover, the destination storage must accommodate double the source virtual machine disk size. VMware Cloud Director Availability 4.2 and later do not consume double the disk size during failover.

  • Example required space in the datastore, for a source virtual machine with a 2 TB virtual disk. When the replication is created, VMware Cloud Director Availability allocates 2 TB in the destination storage. VMware Cloud Director Availability allocates additional 2 TB when starting a test failover task. After finishing the test failover task, the additional 2 TB space is unallocated.
  • Example for a VMware vSAN storage, with the same virtual machine. The same storage implication applies, where the vSAN must accommodate double the virtual machine disk size. When the replication is created in this example, VMware Cloud Director Availability allocates 2 TB multiplied by the vSAN_Protection_Level_Disk_Space_Penalty. When starting a test failover task, additional 2 TB are allocated multiplied by the vSAN_Protection_Level_Disk_Space_Penalty.