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 shared recovery site configuration, you have multiple protected sites that you configure to recover to a single, shared recovery site. For example, an organization can provide a single recovery site with which multiple protected sites for remote field offices can connect. Another example for a shared recovery site is for a service provider that offers business continuity services to multiple customers.

In a shared recovery site configuration, you deploy one Site Recovery Manager Server instance on each protected site, each of which connects to a different vCenter Server instance. On the recovery site, you set up multiple VMware Site Recovery instances to pair with each Site Recovery Manager Server instance on the protected sites. All the VMware Site Recovery instances on the shared recovery site connect to a single vCenter Server instance. Each Site Recovery Manager Server instance in a pair must have the same Site Recovery Manager extension ID, which you can set when you install Site Recovery Manager Server.

You can convert an existing one-to-one configuration of Site Recovery Manager into a shared recovery site configuration. To convert a one-to-one configuration to a shared recovery site configuration, you deploy additional Site Recovery Manager Server and vCenter Server instances as protected sites, and pair them with additional VMware Site Recovery instances that all connect to the existing vCenter Server instance on the recovery site. Each pair of Site Recovery Manager Server instances in the shared recovery site configuration must use a different Site Recovery Manager extension ID. For example, if you installed a one-to-one configuration that uses the default Site Recovery Manager extension ID, you must deploy all subsequent Site Recovery Manager Server 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

  • Head office

    • 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..

Figure 1. Example of Using VMware Site Recovery in a Shared Recovery Site Configuration
Architecture of SRM in a Shared Recovery Site Configuration