Book Image

Disaster Recovery Using VMware vSphere Replication and vCenter Site Recovery Manager - Second Edition

By : Abhilash G B
Book Image

Disaster Recovery Using VMware vSphere Replication and vCenter Site Recovery Manager - Second Edition

By: Abhilash G B

Overview of this book

VMware vCenter Site Recovery manage is an orchestration tool used to automate disaster recovery in a manner that no other solution does. It is programmed to leverage array-based replication and VMware's proprietary vSphere Replication engine. The book begins by talking about the architecture of SRM and guides you through the procedures involved in installing and configuring SRM to leverage array-based replication. You will then learn how to protect your virtual machines by creating Protection Groups and validate their recoverability by testing recovery plans and even performing failover and failback. Moving on, you will learn how to install and configure vSphere Replication as a standalone disaster recovery solution. It also guides you through the procedures involved in configuring SRM to leverage vSphere replication. Finally, you will learn how to deploy and configure vRealize Orchestrator and its plugin for SRM and vSphere Replication.
Table of Contents (13 chapters)
Disaster Recovery Using VMware vSphere Replication and vCenter Site Recovery Manager Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Reprotecting an SRM site


After you failover the workload from a protected site to the recovery site, the recovery site has no protection enabled for the new workload that it has begun hosting. SRM provides a method to enable protection of the recovery site. This method is called reprotect.

A reprotect operation will reverse the direction of the replication, hence the recovery site is designated as the new protected site. The reprotect operation can only be done on a recovery plan with the Recovery complete status. Also, keep in mind that a reprotect operation can only be executed when you have repaired the failed site and made it available to become a recovery site.

For instance, let's assume that site-A and site-B are the protected and recovery sites, respectively. If workload at site-A were failed over to site-B, then to reprotect site-B, site-A should be made accessible. This would mean fixing the problems that caused the failure at site-A.

Here is how you perform the reprotect operation...