Deploy vSphere Replication for virtual machine replication in Site Recovery Manager. Consider the requirements for the operation of the management components that are failed over.

Networking Configuration of the vSphere Replication Appliances

vSphere Replication uses a VMkernel management interface on the ESXi host to send replication traffic to the vSphere Replication appliance in the recovery region. To isolate vSphere Replication traffic so that it does not impact other vSphere management traffic, configure the vSphere Replication network in the following way.

  • Place vSphere Replication traffic on a dedicated VMkernel adapter.

  • Ensure that the vSphere Replication VMkernel adapter uses a dedicated replication VLAN in the region.

  • Attach the vSphere Replication server network adapter to the dedicated vSphere Replication VLAN in the region

  • Enable the service for vSphere Replication and vSphere Replication NFC traffic on the dedicated vSphere Replication VMkernel adapter.

vSphere Replication appliances and vSphere Replication servers are the target for the replication traffic that originates from the vSphere Replication VMkernel ports.

For more information about the vSphere Replication traffic on the management ESXi hosts, see Virtualization Network Design.

Table 1. Networking Design Decisions for vSphere Replication

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-OPS-DR-009

Set up a dedicated vSphere Replication distributed port group. 

Ensures that vSphere Replication traffic does not impact other vSphere management traffic. The vSphere Replication servers potentially receive large amounts of data from the VMkernel adapters on the ESXi hosts.

You must allocate a dedicated VLAN for vSphere Replication.

SDDC-OPS-DR-010

Set up a dedicated VMkernel adapter on the management ESXi hosts

Ensures that the ESXi server replication traffic is redirected to the dedicated vSphere Replication VLAN.

None.

SDDC-OPS-DR-011

Attach a virtual network adapter for the vSphere Replication VMs to the vSphere Replication port group.

Ensures that the vSphere Replication VMs can communicate on the correct replication VLAN.

vSphere Replication VMs might require additional network adapters for communication on the management and replication VLANs.

Placeholder Virtual Machines

Site Recovery Manager creates a placeholder virtual machine on the recovery region for every machine from the Site Recovery Manager protection group. Placeholder virtual machine files are small because they contain virtual machine configuration metadata but no virtual machine disks. Site Recovery Manager adds the placeholder virtual machines as recovery region objects to the Management vCenter Server.

Snapshot Space

To perform failover tests, you must provide additional storage for the snapshots of the replicated VMs. This storage is minimal in the beginning, but grows as test VMs write to their disks. Replication from the protected region to the recovery region continues during this time. The snapshots created during testing are deleted after the failover test is complete.

Sizing Resources for vSphere Replication

Select a size for the vSphere Replication nodes to facilitate virtual machine replication of the SDDC management components according to the objectives of this design.

Table 2. Compute Resources for a vShere Replication 4 vCPU Node

Attribute

Specification

Number of vCPUs

4

Memory

4 GB

Disk Capacity

18

Environment

Up to 2000 replications between nodes

Sizing is done according to IT organization requirements. However, this design uses calculations for a single region. The design then mirrors the calculations for the other region. You must protect a total of 13 virtual machines. For information about the node configuration of the management components per region that is used in the calculations, see SDDC Nodes with Failover Support.

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-OPS-DR-012

Deploy vSphere Replication node of the 4 vCPU size.

Accommodate the replication of the expected 13 virtual machines that are a part of the following components:

  • vRealize Automation Components

  • vRealize Operations Manager Components

None.