Welcome to my site. I started this site as an online archive for me and all things virtual. I kept getting requests for help around some of the more standard issues we all hit in dealing with Cloud automation, particularly around the VMware vCloud Stack so I decided to make my forum public...and here we are.

My name is Lee Friend and I'm based in London, UK. I am a Cloud orchestration specialist in the end to end management, automation and integration of virtualisation stacks covering all pieces of the puzzle from IPAM (InfoBlox / QIP / IP Control), DNS, AD, resiliency & DR (SRM automation), management system integration (including ServiceNow, BMC Remedy, ticketing systems) and on and on.

Having worked since the very early days of virtualisation, I specialise in the vRealize suite (vRO,vRA,vCD,vR OPs,vCloudClient,SRM,and on) with the aim of orchestrating wherever it's needed. I have helped out large financials, global exchanges and cloud service providers at an architecture level all the way through to workflow engineering.

SRM eror Recovery plan contains protection groups that are in use by another recovery plan that is either currently

Anything to do with automation with SRM activities
leefriend
Site Admin
Posts: 30
Joined: Sat Dec 20, 2014 4:45 pm

SRM eror Recovery plan contains protection groups that are in use by another recovery plan that is either currently

Postby leefriend » Thu Jun 25, 2015 12:07 pm

Error: Recovery plan contains protection groups that are in use by another recovery plan that is either currently running

Generally seen when the recovery has failed but the database has not been updated. Always backup the database before making changes!

1) Stop the SRM service on both recovery and protected site.
2) Connect to the database server for the recovery site SRM.
3) Backup database.
4) In SQL Management Studio, edit the table [pdr_planproperties]
- change STATE to readyReceiving (from groupsInUse).
- change PEERSTATE to readySending.
5) Edit the table [pdr_protectiongroup]
- change STATE to 6.
6) Start SRM service on both SRM servers.

Return to “Everything SRM”



cron