This post is also available in: Italian

Reading Time: 2 minutes

Around a month ago I’ve got an issue with VMware SRM 5.0.1 during a test of the Recovery Plan.

In my case the storage was well configured for the replication, but not to permit the reverse reverse replication. So the reprotect task was locked and there was no way to remove this state because also the Delete Protection group was greyed out. If you fix the storage part usually the issue could be fixed in a clean way, but in my case the original LUN was removed and was not possible resume or fix the operation (also if you build a new LUN the ID could not be same). Also a SRM reboot was unsuccessful because the state was in the database.

I’ve looked around but I’ve not found a clean solution, so I’ve simple build a new Protection Group to look in the SRM DB and compare the wrong state with the clean one. With a little of patiance you can find the tables (note that are more than one and both on the production and the disaster recovery site) and fix the values. After that you can finally delete the Protection Group to really clean the database.

Now I’ve notice that there is a recent KB 2032621 (Protection group in vCenter Site Recovery Manager 5.x hangs in reprotecting state during the reprotect task), available from Aug 9 2012, that describe exactly this situation and the same solution.


Virtualization, Cloud and Storage Architect. Tech Field delegate. VMUG IT Co-Founder and board member. VMware VMTN Moderator and vExpert 2010-24. Dell TechCenter Rockstar 2014-15. Microsoft MVP 2014-16. Veeam Vanguard 2015-23. Nutanix NTC 2014-20. Several certifications including: VCDX-DCV, VCP-DCV/DT/Cloud, VCAP-DCA/DCD/CIA/CID/DTA/DTD, MCSA, MCSE, MCITP, CCA, NPP.