Configuring SRM and vSphere Replication 9.0 ~ 9.0.2.x for multiple protected vCenters replicating to a single recovery vCenter

Products

• VMware vCenter Server

Issue/Introduction

This article provides guidance on the required configuration of Site Recovery Manager (SRM) and vSphere Replication (VR) versions 9.0 through 9.0.2.x to support multiple protected vCenters replicating to a single recovery vCenter.

Environment

 

• VMware vSphere Replication 9.0 ~ 9.0.2.x

• VMware Site Recovery Manager 9.0 ~ 9.0.2.x

• Two independent protected sites, each with its own vCenter, VR, and SRM appliances

• One recovery site with a single vCenter Server

• The recovery vCenter must be able to accept replications from both protected sites

 

Resolution

Configuration Overview

Before starting deployment, plan and define two different SRM Extension IDs that will be used consistently across the paired sites.

• Extension ID 1 (for example,  com.vmware.vcDr-01) for SRM pair A ↔ A’

• Extension ID 2 (for example, com.vmware.vcDr-02) for SRM pair B ↔ B’

Deployment topology:

• Protected Site A: vCenter A – VR A – SRM A

• Protected Site B: vCenter B – VR B – SRM B

• Recovery Site: vCenter R – VR R – SRM A’ and SRM B’

Each SRM instance must be configured with the appropriate Extension ID to match its counterpart on the recovery site. Please refer to the following diagram for visual reference.

 

Configuration Steps

1. Deploy SRM and VR Appliances

   • Deploy one vSphere Replication (VR) and one SRM appliance for each protected vCenter.

   • On the recovery vCenter, deploy one shared VR instance and the corresponding number of SRM appliances to match the protected vCenters.
     (for example, for two protected sites, deploy two SRM instances.)

2. Register VR with vCenter

   • Access the 5480 VAMI page of VR A, click RECONFIGURE, and provide the vCenter A connection details to register VR A with vCenter A.

   • Repeat the same procedure for VR B connect to vCenter B, and VR R connect to vCenter R.

   • The Extension ID for vSphere Replication is "com.vmware.vcHms" and cannot be modified.

3. Register SRM with vCenter and configure a custom Extension ID

   • Access the 5480 VAMI page of SRM A, click RECONFIGURE, and provide the vCenter A connection details to register SRM A with vCenter A.

     • In the Extension ID field, enter the first custom Extension ID, for example, com.vmware.vcDr-01.

   • On the recovery site, perform the same configuration for SRM A’, connecting it to vCenter R and entering the same Extension ID as above.

   • Next, repeat the process for SRM B and SRM B’:

     • Connect SRM B to vCenter B and SRM B’ to vCenter R.

     • In both cases, enter the second custom Extension ID, for example, com.vmware.vcDr-02

4. Site Pairing Procedure

   • Log in to SRM A on the protected site and click 'NEW SITE PAIR'.

   • When prompted for Peer vCenter Server, specify the recovery vCenter Server.

   • Under Services, only SRM A’ and VR R will appear because SRM A and SRM A' share the same Extension ID.

   • Repeat the same process for SRM B and SRM B’.

5. Replication Validation

   • After pairing, configure VM replication using the corresponding VR appliances.

   • It is recommended to organize replicated virtual machines from each protected site into separate folders and resource groups to avoid name conflict.