General steps for removing and redeploying SRM

I inherited an SRM deployment that constantly has replication issues and is not something that we’re confident we can fail over to. I would like to remove it and install a fresh SRM 8.2 instance between our primary and DR sites. I talked to VMware support about it and these were the general steps I received to remove SRM and the replication appliance:

1) Delete Protection Groups out of SRM
2) Delete Recovery Plans out of SRM
3) Remove all “Replications” from SRM
4) Uninstall SRM from Windows server it lives on
5) Unregister VRMS from VAMI page
5) Delete VRMS VM
6) Repeat any applicable steps on DR side

To redeploy, I just need to reverse these steps, correct?

1) Deploy VRMS VM in both PROD and DR
2) Register VRMS VM (if not done via setup) in PROD and DR vCenters
3) Deploy SRM appliance in both PROD and DR, registering them with their associated vCenter servers
4) Run through the SRM setup steps on the PROD side to create my site pair, replications, recovoery plans, and protection groups

Is that the gist of it? Does anyone else have any experience with this?

View Reddit by jamesgambleView Source

Related Articles


  1. I did the same thing, a few months ago, with vCenter 6.7. Took me several calls to VMware to help with the re-install. Best of luck if one site goes down and you need to reboot the entire SRM system. The errors are super fun to troubleshoot.

    Here are the steps that I documented on configuring SRM 8.2. There are basically two parts of SRM. vSphere recovery and Site Recovery Manager. Install vSphere recovery first and get it working. Then install SRM. Make sure you create DNS entries for all four servers, before you start, so it has time to replicate through DNS (Step 1)

    1. Decide which IP addresses and names you will use and create DNS entries to them (for all four servers, which includes replication and SRM servers at each site)
    2. Download the vSphere replication appliance ISO and extract it. 
    1. Connect to the vCenter server and deploy a new OVF template. 
    2. Browse to the folder that contains the files. Make sure to select all 5 files and not just the OVF file.
    3. Walk through the wizards to configure and install the appliance.
    3. Once the install is finished, do the same thing on the other site’s vCenter server.
    4. Connect to the website of each replication appliance by going to https://ipaddress:5480.
    1. Log in as root and the password you used during deployment.
    2. Click on the Configuration tab. Enter the administrator@vsphere.local password and hit Save and Restart. Accept the certificate. Once all services are running, close the browser.
    5. Once that is configured, browse to the vCenter server and click on the dropdown at the top and click on Site Recovery. You should have vCenter Replication listed as an option. From here, you could start replicating VMs.
    6. Installing the SRM appliances is the same as the vSphere Replication.
    1. Once installed, browse to the web interface by going to https://ipaddress:5480 and login with admin and the password you used during deployment.
    1. On the main page, click “configure appliance” and walk through the wizard to configure the link between the appliance and the vCenter server. Make sure you use FQDNs for everything.
    7. Once SRM is configured and linked with the vCenter server, browse to the vCenter server and click on the dropdown at the top. Go to Site Recovery and you should see both vSphere Replication and Site Recovery Manager listed.
    8. Open Site Recovery and login with administrator@vsphere.local.  
    1. Click on “New Site Pair”
    2. Enter the FQDN of the remote SRM site and the administrator@vsphere.local account and password.
    3. Check all the boxes and click finish.
    9. Once a site pair has been established, click on View Details. Login again.
    10. On the left tree, configure Network Mappings, Folder Mappings, Placeholder Datastores
    11. From here, you can setup Protection Groups, Recovery Plans, and start replicating VMs.

Leave a Reply