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

How does replication work?


Once VM replication is successfully configured, it first does an initial full sync of the source VMDKs to the target datastore. If you already have the base VMDKs precopied to the destination datastore, then only the changed blocks are replicated. The replication happens over the network using the Network File Copy (NFC) protocol. The changed blocks are transferred using ESXi's management VMkernel port group.

Once the initial sync is complete, the VR Agent tracks the changed blocks using the vSCSI filter driver. It tracks, writes, and maintains a bitmap of the changed blocks. Every time a replica is created, the data transferred is copied to a redo log file. This is done to make sure that a VM at the recovery site is not corrupted in the event of a network disruption. The redo log is committed to the base disk only after the changed blocks are fully copied, thereby making each replica crash consistent. When you configure replication for a VM you get to choose the...