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

Understanding protection groups


Unlike vSphere Replication, SRM cannot enable protection on individual VMs. All the VMs that are hosted on the datastores in a datastore group are protected. The protection is enabled at the datastore group level because with array-based replication, the LUNs backing the datastores are replicated. The array doesn't know which VMs are hosted on the datastore. It just replicates the LUN block by block. So, at the SRM layer, the protection is enabled at the datastore level. In a way, a protection group is nothing but a software construct to which datastore groups are added, which in turn includes all the VMs stored on them in the protection group.

When creating a protection group, you will have to choose the datastore groups that will be included. Keep in mind that you cannot individually select the datastores in a datastore group. If it were ever allowed, then you will have VMs with not all of their files protected. Let's assume that you have a virtual machine...