To accommodate the changes of your disaster recovery strategy, you can either add new DR plans or update the existing ones or retire existing DR plans.
Through a DR plan you can preconfigure various aspects of disaster recovery for a single-click failover in the event of a disaster. DR plan encompasses virtual machines configured for disaster recovery, the AWS account used for disaster recovery, the replication frequency, the network settings, instance-related failover settings, and the order in which you want to recover the instances.
A DR plan comprises of the following pages , wherein through each page , you can manage a specific aspect of the plan.
|Page||Tasks you can perform|
Update plan description and replication settings.
From this page, you can also trigger the failover.
Add new VMs and update the settings of existing VMs that are part of a DR plan and critical for disaster recovery.
See, Manage virtual machines.
Update the network mappings of the VCenter source network to a VPC and subnet on the target AWS account.
See, Manage network mappings.
The recovery workflow works as a runbook and can be executed based on your application’s requirements. It enables you to define steps to logically group the virtual machines in a DR plan to perform operations in a defined order.
See, About recovery workflow.
The virtual machines in the vCenter data center are backed up to the Druva Cloud. The virtual machine images based on the backup schedule are converted to AWS EBS volumes. The EBS snapshots are kept-at-the-ready inside the customer’s AWS account (Virtual Private Cloud) for immediate spin-up of AWS EC2 instances during a failover.
From this page, you can also trigger the failback.