Create Recovery Plans



Recovery plans consist of one or more ordered groups that contain virtual machines or physical servers that you want to fail over together. Recovery plans do the following:

  • Define groups of machines that fail over and then start up together.
  • Model dependencies between machines by grouping them together in a recovery plan group. For example if you want to fail over and bring up a specific application you would group the virtual machines for that application in the same recovery plan group.
  • Automate and extend failover. You can run a test, planned, or unplanned failover on a recovery plan. You can customize recovery plans with scripts, Azure automation, and manual actions.
Customize recovery plans

The way in which we create a recovery plan depends on your Site Recovery deployment.

  • Replicating VMware VMs and physical servers—You create a plan and add replication groups that contain virtual machines and physical servers to a recovery plan.
  • Replicating Hyper-V VMs (in VMM clouds)—You create a plan and add protected Hyper-V virtual machines from a VMM cloud to a recovery plan.
  • Replicating Hyper-V VMs (not in VMM clouds)—Create a plan and add protected Hyper-V virtual machines from a protection group to a recovery plan.
  • SAN replication—Create a plan and add a replication group that contains virtual machines to the recovery plan. You select a replication group rather than specific virtual machines because all virtual machines in a replication group must fail over together (failover occurs at the storage layer first).

After you’ve added protected virtual machines or replication groups to the default recovery plan group and created the plan you can customize it:

  • Add new groups—You can add additional recovery plan groups. Groups you add are numbered in the order in which you add them. You can add up to seven groups. You can add more machines or replication groups to these new groups. Note that a virtual machine or replication group can only be included in one recovery plan group.
  • **Add a script **—You can add scripts that before or after a recovery plan group. When you add a script it adds a new set of actions for the group. For example a set of pre-steps for Group 1 will be created with the name: Group 1: Pre-steps. All pre-steps will be listed inside this set. Note that you can only add a script on the primary site if you have a VMM server deployed.
  • Add a manual action—You can add manual actions that run before or after a recovery plan group. When the recovery plan runs, it stops at the point at which you inserted the manual action, and a dialog box prompts you to specify that the manual action was completed.

Organizations need a business continuity and disaster recovery (BCDR) strategy that a determines how apps, workloads, and data stay running and available during planned and unplanned downtime, and recover to normal working conditions as soon as possible. Your BCDR strategy center’s around solutions that keep business data safe and recoverable, and workloads continuously available, when disaster occurs.

Site Recovery is an Azure service that contributes to your BCDR strategy by orchestrating replication of on-premises physical servers and virtual machines to the cloud (Azure) or to a secondary datacenter. When outages occur in your primary location, you fail over to the secondary site to keep apps and workloads available. You fail back to your primary location when it returns to normal operations. Site Recovery can be used in a number of scenarios and can protect a number of workloads.