Limitations of Using Site Recovery Manager in Shared Recovery Site Configuration

When you configure Site Recovery Manager to use a shared recovery site, Site Recovery Manager supports the same operations as it does in a standard one-to-one configuration. Using Site Recovery Manager with a shared recovery site is subject to some limitations.

• Site Recovery Manager supports point-to-point replication. Site Recovery Manager does not support replication to multiple targets, even in a multi-site configuration.
• For each shared recovery site customer, you must install Site Recovery Manager Server once at the customer site and again at the recovery site.
• You must specify the same Site Recovery Manager extension ID when you install the Site Recovery Manager Server instances on the protected site and on the shared recovery site. For example, you can install the first pair of sites with the default Site Recovery Manager extension ID, then install subsequent pairs of sites with custom extension IDs.
• Each Site Recovery Manager Server instance on the protected site and on the shared recovery site requires its own database.
• A single shared recovery site can support a maximum of ten protected sites. You can run concurrent recoveries from multiple sites. See Operational Limits of Site Recovery Manager for the number of concurrent recoveries that you can run with array-based replication and with vSphere Replication.
• In a large Site Recovery Manager environment, you might experience timeout errors when powering on virtual machines on a shared recovery site. See Timeout Errors When Powering on Virtual Machines on a Shared Recovery Site.
• When connecting to Site Recovery Manager on the shared recovery site, every customer can see all of the Site Recovery Manager extensions that are registered with the shared recovery site, including company names and descriptions. All customers of a shared recovery site can have access to other customers’ folders and potentially to other information at the shared recovery site.