Part 14 – Configuring a Recovery Plan

Creating a Recovery Plan is a very good thing but how do make it work the way we want it to? Well, every Recovery Plan has to be configured for the fact that, virtual machines depend on other machines in many ways, for example, the DB server has to powered on first for the app server and web server to connect to it and in some cases, we want to run some start-up scripts so that the machine can become available to users. All such things have to be fed to the recovery plan. So let’s see how that is done.

Recovery Plan run a series of steps that are performed in a specific order, the order cannot be changed, however, we can insert our own steps like displaying messages and run commands. Each Recovery Plan Steps are run different and not all steps are same i.e, steps for recovery differs from steps for reprotect. It is very much important to understand how recovery steps run, their order and context in which they run to be able to customize a recovery plan.

Recovery Order

When a recovery plan is run, the virtual machines on the protected site are powered off according to the priority set with least priority machines turned off first. SRM avoids this step when a recovery plan is tested. Site Recovery Manager powers on the VMs at the recovery site also according to the priority set and is done is groups. If there exists any dependencies within the groups, SRM waits untill they are resolved or failed and any dependencies out of a priority group are ignored. SRM always tries to power on as many VMs as possible.

SRM can run custom steps on either the SRM server or the VMs that are part of the recovery plan. If a priority is changed on the virtual machine, the priority applies to the virtual machine in all the recovery plans. SRM uses VMware Tools heartbeat to discover when a virtual machine is powered on or off and thus it makes sure that the next priority group virtual machines are not powered on before higher priority VMs are completely up.

The different recovery steps that are run for Test, Recovery, Cleanup and Reprotect can be viewed as below .

2016-10-13-01_40_11-vsphere-web-client

Once the Recovery Plan is created, it can be customized as per our needs.

 2016-10-12-23_42_25-vsphere-web-client

Priority for the VM power on can be set from the actions menu as below.

2016-10-12-23_43_18-vsphere-web-client

To completely configure the VM settings for the recovery, use the settings icon after selecting the VM. As you can see the priority can be set from this screen as well. Startup action can be set, pre power on steps and post power on steps can be configured here.

2016-10-12-23_47_59-vsphere-web-client

To customize the IP settings on a VM at the recovery site, use the next tab IP Customization. If there is no IP customization, SRM uses the same IP settings during the test and recovery as that of the protected site.

2016-10-12-23_48_50-vsphere-web-client

I have configured some of the settings in my lab and below is how the recovery plan is finally.

2016-10-13-21_34_59-vsphere-web-client

Hope this was informative. Thanks!

Part 1 – Introduction to SRM 6.1

Part 2 – SRM 6.1 Home Lab Setup

Part 3 – Installing SRM 6

Part 4 – Installing HP VSA on VMware Worstation – Step By Step

Part 4 – Installing HP Virtual Store VSA on ESXi – Step By Step

Part 5 – Install HP CMC for VSA – Step by Step

Part 6 – Creating Management Groups, Volumes and Presenting them to ESXi – HP VSA

Part 7 – Scheduling Array Based Replication – HP VSA

Part 8 – Pairing Sites and Installing HP-SRA on SRM 6

Part 9 – Configure and Rescan SRM Array Managers

Part 10 – Understanding Inventory Mappings and Other Terms.

Part 11 – Configure Inventory Mappings

Part 12 – Creating Protection Group

Part 13 – Creating a Recovery Plan

Part 14 – Configuring a Recovery Plan

Part 15 – Test a Recovery Plan

Part 16 – Cleanup after testing a Recovery Plan

Part 17 – Running a Recovery

Advertisements

#ip-costomization, #recovery-plan, #recovery-steps, #srm-6-1