A DR Plan defines the configuration and orchestration steps required for successful VM recovery.

You can create, name, edit, duplicate, save, and run DR Plans. Environment variables in a plan map differences between the sites for smooth recovery, ensuring that vSphere configurations and parameters are mapped consistently between sites.

Plans run either for recovery as an actual DR plan operation, or they run as a test recovery, which performs all of the plan’s recovery operations in a test site for validation.

Execution pacing is configurable. When a plan runs, a running instance of the plan launches and typically continues executing its recovery steps to completion. A recovery or test plan can also continue to specific points in the process and wait for user input, or it can stop and wait for a specified time limit, and then continue until the next stop or to completion. You can also add pre- or post-scripting to a VM’s recovery step.

VMware Cloud DR performs a set of compliance checks for all active plans and resources, and it reports on environmental changes, such as vSphere misconfigurations or network outages. Compliance checks detect any compromised plan integrity at the time of misconfiguration or equipment failure. Compliance checks also give the user an opportunity to address issues and restore the plan's integrity before disaster occurs. For developing and retaining the skill set of related DR activities, you should still perform periodic full DR exercises with the staff involved.

VMware Cloud DR can maintain multiple plans of different types, and multiple plans can be in various stages of execution at any given time, even concurrently.