top of page


No tags yet.

VMware Cloud on AWS DRaaS (SRM) Deployment

One of the Best use cases for Hybrid cloud is when we want to protect our on-prem workloads on cloud, so during any disaster situations we can easily recover them and reduce the total downtime of a service. We have DRaaS introduced with VMware Cloud on AWS as SRM solution and it works seamlessly between On-prem and Cloud Data-centers.

In this Blog I want to demonstrate a step by step deployment of DRaaS on VMware Cloud on AWS and Onprem vSphere , lets get started with the requirements, and first lets talk about the required ports so that we can avoid any hiccups during our deployment.

Requirements :

# IPSEC VPN / Direct Connect between Onprem and VMC 

# Your SDDC should be updated with onprem DNS

# Following Ports should be Opened at on prem side and SDDC Side

Now lets get started with the deployment and the connectivity steps.

We will first activate  site recovery on the VMware Cloud on AWS Side and to do that :

1) Login to portal and go to VMware cloud on AWS.

2) Select your desired SDDC.

3) Click on Add Ons.

4) Click on activate button in Site recovery section.

After clicking Activate a new Window will pop up which gives you the option to set an extension key , Extension Key could be useful in case you want to connect your second site to this SDDC. For each protected site, you must install one instance of Site Recovery Manager Server at the protected site and one instance of Site Recovery Manager Server at the recovery site. You can only pair Site Recovery Manager Server instances that have the same Site Recovery Manager extension ID. Each protected site must include its own vCenter Server instance.

Creating Extension ID

**Make sure whatever Extension ID you are providing here you should use same at the onprem side while installing SRM otherwise you might end up having issues in Site paring where the SRM for remote site will not be visible.

 Now once you click activate the cloud side SRM will start deploying 

Create following Firewall rules at SDDC Side ( is the sub-net for my onprem components, please check the first port diagram if you want to do it for each component)

Now lets Jump Back to the On-prem side and install the 2 required components there (Use this Doc 

1) SRM server : Install this service on a Windows Server 2012 and Register it with onprem vCenter

and now you will be able to see the Site Recovery add on in vCenter HTML Client (You might have to log off and log back in)

2) VR appliance : Deploy the VR as Appliance 

And Configure and register VR appliance with vCenter 

 After VR Appliance configuration we are done on the installation part and now lets do the site pairing 

Before we jump on to the site pairing part lets make sure that we are good at DNS part 

1) It is recommended to make  the DNS entry of all the Onprem SRM components.

2) For cloud Side components Either your Onprem DNS should be able to forward the requests to Internet DNS. or you will have to create an       

    entry for SRM and VR Manually by adding a Zone for your SDDC.

Lets do the Site pairing now..

- Go to Site recovery Plugin and open site recovery and then click new site pair 

- Select the Local vCenter in first site box (if you are initiating site pairing from on-prem side)

- In the second site section paste the VMware cloud side vCenter URL, Username and password 

Click Next and You will see Cloud side Components (SRM and VR listed in vCenter Server and Services Window 

Select Both the service components and click Next after a review Window Click Finish 

And we are done with the site pairing now 

And in the Summary page You should now see all the information

And now we can do  normal site recovery operations by creating protection group, recovery plan and protect our Onprem VMs to Cloud on VMware Cloud on AWS SDDC.

#DRAAS #VMC #SRM #VMConaws #disasterrecovery #VMConAWS #vmconaws #VMwareCLoudonAWS #VMwarecloudonAWS

bottom of page