So we have already covered SRM 5 - Priorities and Recovery Order in a previous post. However what if we want to manipulate the startup order more specifically within a priority group?
Well that's what we have "VM Dependencies" for for each virtual machine within the recovery plan.
Just to re-cover the past and present..
Site Recovery Manager 5 brought a change from 3 levels of priorities (High, Medium, Low) to 5 levels of priorites (1-5 with 1 being the highest priority).
So now instead of having additional seperate recover plans to allow for specific recovery priorities, we can perhaps now include them within one recovery plan.
However that said, you might put critical infrastructure VMs in priority 1, critical tier 1 business apps at priority 2 and so on, but what about dependencies within each of those priorities?
In priority 2 (critical tier 1 business apps) there might be an application that has a DB VM and a web server VM, in which the web VM depends on the DB VM being available first.
What we could then do is set a VM dependency for the web VM to say it depends on the DB VM, hence they will be started in the required order, one after another.
One thing to note however is by setting VM dependencies is that it will extend the time it takes to run the recovery plan, as there will be an additional time while each VM with a dependency waits before it can power on itself. Say 5 minutes boot time each, so you can easily see how that 15 min recovery time objective (RTO) could be smashed to 30 mins etc the more dependencies you have!
Configuring VM dependencies is easy-peasy..
1. Go you your desired recovery plan.
2. Select the VM that has a dependency on another VM and choose Configure.
(in our case SRMDEMOVM1 depends on SRMDEMOVM2 being booted first)
3. In the VM Recovery Properties dialog for the VM, navigate to "VM Dependencies"
4. Click Add, and select the VM that it depends on. Click Add.
5. The VM dependency will be added and show the status of that VM, priority group and protection group. Click Ok.
Share this blog post on social media:
TweetAll advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.