Home » Hybrid Cloud » EHC Disaster Recovery Edition – vRA and SRM Integration

EHC Disaster Recovery Edition – vRA and SRM Integration


Returning to the blog post series about EHC, this blog will cover the EHC Federation Edition with Disaster Recovery. In this post, we will be looking at the intergration between VMware SRM and vCAC. Yes that’s right. Some of you might be unaware that vCAC or vRA is supported for DR by VMware SRM. Let us look at the conceptual diagram how this would work.

Note: This blog doesn’t discuss the DR/HA Availability of vCAC. That will be discussed in subsequent posts.

Conceptual We will need to create 2 vCenter endpoints in vRA. This will ensure that both the protected and the recovery site VMs can be managed by vCAC instance. So lets go ahead and create the 2 endpoints in vRA. 2 Endpoints in vRA Note that both the vCenters have been named DR for vCAC controller environments are supported in 3 ways :

  • Protected Mode
  • Recovery Mode
  • Test Mode.

These are not dis-similar to the native protected methods in VMware SRM. Most of the workload migration and restart of the VMs is automatic as it is natively done by SRM. However there are a few manual steps that are required to ensure that vCAC can monitor and manage the “recovered” workloads. Lets now look at the behaviour of vRA during various SRM Phases. SRM Phases and vRA State

Now lets look at an example of failover and the steps that are required to ensure the vRA is still in sync after failover / migration is finished.

Once the planned migration or disaster recovery steps are finished inside SRM, check vRA appliance for any errors. You will see a similar error on all the VMs managed by vRA.

vRAError

To remediate this error, the following steps have to be done:

Turn off Automatic Data Collection for Site A vCenter (under compute resources).

Run Data Collection Manually for Site B vCenter (under compute resources).

Perform manual failover for the VM on Site A as shown below

Go to Infrastrucuture – Machines – Managed Machines.

Hover over the VM and select Change Reservation.

ManualFailover

Once the pane changes to the reservation, change the appropriate values as shown below ( these are the values in the lab environment and will be different to your actual values)

ManualFailover1

Note: If the blueprint is shared, that value doesnt need to be changed.

Once these steps are completed, turn data collection on for Site A vCenter.

This can be automated using the tool below https://developercenter.vmware.com/web/dp/tool/cloudclient/3.2.0. Thanks to Ben Meadowcroft (@benmeadowcroft) for bringing it to my knowledge.

For more information on vCenter/SRM/VCO/vRA integration visit the links below


7 Comments

  1. sidbrydon says:

    Reblogged this on vAware and commented:
    Very interesting article!

  2. Nice article. One other useful tool to help automate the failover is the vRealize Cloud Client available at https://developercenter.vmware.com/web/dp/tool/cloudclient/3.2.0

    You can call this tool from your SRM recovery plans and it will take care of updating the reservations and so on for you.

  3. Bernie says:

    hello. from the procedure. I have a doubt. this works with ABR SRM ?. because to create the reserve in the secondary site must be configured datastores but ARB are not visible until done failover.

  4. Raymond says:

    Any sample script that call from SRM recovery plan to automate the changes of reservation?

Leave a comment

Your email address will not be published. Required fields are marked *

Koodzo

Check Out koodzo.com!

Categories

Archives