Overview of Recovery Flows : Flow for a Disaster Recovery Operation
  
Flow for a Disaster Recovery Operation
Disaster recovery using Zerto Virtual Replication enables recovering from a disaster to any point between the moment just before the disaster and a specified amount of time in the past up to 30 days. The recovery is done in real time at the recovery site with a minimal RTO.
A recovery operation is one of the following:
A failover.
A planned move of the protected virtual machines from the protected site to the recovery site.
A clone of the protected virtual machine to the recovery site.
Virtual machines are protected in VPGs, which are defined in the protected site. Once a VPG is created, Zerto Virtual Replication creates a copy of the protected virtual machines under the management of a Virtual Replication Appliance, VRA, on the AWS recovery site. The data managed by the VRA is saved in an S3 bucket.
When a recovery operation is performed, the VRA creates the virtual machines defined in the VPG in EC2 and imports data from the S3 bucket as EBS disks in EC2.
After initializing the VPG, all writes to the protected virtual machines are sent by the VRA on the relevant host for each virtual machine on the protected site to the VRA on the AWS recovery site. The information is saved in the journal for the virtual machine with a timestamp, ensuring write-fidelity. Every few seconds the Zerto Virtual Manager causes a checkpoint to be written to every journal on the recovery site for every virtual machine in the VPG, ensuring crash-consistency.
The data remains in the journal until the time specified for the journal when it is moved to the relevant mirror disks in S3, also managed by the VRA for the virtual machine. In this way, you can recover the virtual machines using the mirror disks and the data from the journal to include the final few hours of data for each virtual machine. Refer to “The Role of the Journal During Protection”, on page 24 for more details about the journal.
The following references the procedures to recover virtual machines protected in a VPG:
“Overview of Disaster Recovery Operations”, on page 73
“Managing Failover to AWS”, on page 97
“Migrating a VPG to AWS”, on page 91
“Cloning a VPG to AWS”, on page 103