A separate Site Recovery Manager instance is required for the protection and recovery of management components in the event of a disaster situation with your SDDC.

Install and configure Site Recovery Manager in a dedicated virtual machine, after you install and configure vCenter Server and the associated Platform Services Controller instances in the region.

Table 1. Design Decisions on the Site Recovery Manager and vSphere Replication Deployment

Decision ID

Design Decision

Design Justification

Design Implication


Deploy Site Recovery Manager in a dedicated virtual machine.

All components of the SDDC solution must support the highest levels of availability. When Site Recovery Manager runs as a virtual machine, you can enable the availability capabilities of vCenter Server clusters.



Deploy each Site Recovery Manager instance in the management cluster.

All management components must be in the same cluster.



Deploy each Site Recovery Manager instance with an embedded PostgreSQL database.

PostgreSQL is the only available database option when deploying the Site Recovery Manager appliance.

You must assign database administrators who have the skills and tools to administer PostgreSQL databases.

Sizing Compute Resources for Site Recovery Manager

To support the orchestrated failover of the SDDC management components according to the objectives of this design, you must size the host operating system on which the Site Recovery Manager software runs.

Table 2. Compute Resources for a Site Recovery Manager Node



Number of vCPUs

2 (running at 2.0 GHz or higher)


8 GB

Number of virtual machine NIC ports


Disk size

20 GB

Operating system

VMware Photon OS

Sizing is usually done according to IT organization requirements. However, this design uses calculations that are based on the management components in a single region. The design then mirrors the calculations for the other region. Consider the following management node configuration per region:

Table 3. SDDC Nodes with Failover Support

Management Component

Node Type

Number of Nodes

Cloud Management Platform

vRealize Automation Appliance


vRealize IaaS Web Server


vRealize IaaS Management Server


vRealize IaaS DEM


Microsoft SQL Server


vRealize Business for Cloud Appliance


vRealize Suite Lifecycle Manager

vRealize Suite Lifecycle Manager Appliance


vRealize Operations Manager

vRealize Operations Manager Master


vRealize Operations Manager Master Replica


vRealize Operations Manager Data


You must protect a total of 15 virtual machines.

You use vSphere Replication as the replication solution between the Site Recovery Manager sites, and you distribute the virtual machines in two protection groups.

Table 4. Design Decisions on Compute Resources for the Site Recovery Manager Nodes

Decision ID

Design Decision

Design Justification

Design Implication


Deploy the Site Recovery Manager virtual appliance according to the following specifications:

  • 2 vCPUs

  • 8 GB memory

  • 20 GB disk

  • 1 VMXNET 3 NIC

Accommodates the protection of management components to supply the highest levels of availability. This size further accommodates the following setup:

  • The number of protected management virtual machines as defined in Table 3

  • Two protection groups

  • Two recovery plans

You must increase the size of the nodes if you add more protection groups, protected virtual machines or recovery plans.

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 vCenter Server inventory.