With VMware Site Recovery, you can connect multiple protected and recovery sites to a single VMware Cloud on AWS SDDC.
You can recover virtual machines from multiple protected sites to the same VMware Cloud on AWS SDDC or recover different sets of virtual machines from a single VMware Cloud on AWS SDDC to multiple recovery sites. The former is known as a shared recovery site, a many-to-one, fan-in, or an N:1 configuration, while the latter is known as a shared protected site, a one-to-many, fan-out, or an 1:N configuration. VMware Site Recovery also supports many-to-many or an N:N configurations, and other complex multi-site topologies such as a single site A being protected to a recovery site B, while also serving as a recovery site for a third site C.
In the standard one-to-one VMware Site Recovery configuration, you use Site Recovery Manager to protect a specific instance of vCenter Server by pairing it with another vCenter Server instance.
In a multi-site topology, you have multiple remote sites that you configure to recover to or protect from a single, shared VMware Cloud on AWS SDDC. For example, an organization can provide a single recovery site in VMware Cloud on AWS to which multiple protected sites representing remote field offices can be connected.
In a multi-site topology, you deploy one Site Recovery Manager Server or VMware Site Recovery instance on each remote site, each of which connects to a different vCenter Server instance. On the shared VMware Cloud on AWS SDDC, you set up multiple VMware Site Recovery instances to pair with each Site Recovery Manager Server instance on the remote sites. All the VMware Site Recovery instances in the shared VMware Cloud on AWS SDDC connect to a single vCenter Server instance. Each Site Recovery Manager Server or VMware Site Recovery instance in a pair must have the same plug-in identifier or extension ID, which you can set when you install Site Recovery Manager Server or activate VMware Site Recovery.
You can convert an existing one-to-one configuration of VMware Site Recovery into a multi-site configuration. To convert a one-to-one configuration to a multi-site configuration, you deploy additional Site Recovery Manager Server and vCenter Server instances as remote sites, and pair them with additional VMware Site Recovery instances that all connect to the existing vCenter Server instance on the shared VMware Cloud on AWS SDDC. Each pair of Site Recovery Manager Server or VMware Site Recovery instances in the multi-site configuration must use a different plug-in identifier or extension ID. For example, if you installed a one-to-one configuration that uses the default VMware Site Recovery extension ID, you must deploy all subsequent VMware Site Recovery pairs with different custom extension IDs.
Using VMware Site Recovery with Multiple Protected Sites and a Shared Recovery Site
An organization has two field offices and a head office. Each of the field offices is a protected site. The head office acts as the recovery site for both of the field offices. Each field office has a Site Recovery Manager Server instance and a vCenter Server instance. The head office has two VMware Site Recovery Server instances, each of which is paired with a Site Recovery Manager Server instance in one of the field offices. Both of the VMware Site Recovery Server instances at the head office extend a single vCenter Server instance.
Field office 1
Site Recovery Manager Server A
vCenter Server A
Field office 2
Site Recovery Manager Server B
vCenter Server B
VMware Site Recovery Server C, that is paired with Site Recovery Manager Server A.
VMware Site Recovery Server D, that is paired with Site Recovery Manager Server B.
vCenter Server C, that is extended by VMware Site Recovery Server C and VMware Site Recovery Server D.