ian0x0r wrote:
Did you ver get this reolved Jason? I've got the same situation now with Dell Equallogic kit and I dont really want to go down the root of uninstalling and re-installing SRM to fix this.
Thanks,
Ian
Lee and a few others were able to spend considerable time with me on this. In my instance, I was able to solve the problem without uninstalling/reinstalling the environment. I did so by cleaning up the storage and replication at both sites which SRM managed. One or more of the volumes at one of more of the sites was in a precarious state from a replication standpoint. This was causing the SRA to return a status to SRM which SRM did not like and thus would not proceed until the precarious state was resolved and a more appropriate/proper status code could be returned by the SRA. Once that underlying storage issue was remedied, the force cleanup worked instantly as one might expect it to and I was then able to tear down the recovery plan and the hung protection group, fix the direction of replication as needed for the LUN(s), then simply recreate the protection group and recovery plan.
As I cross posted in the other thread linked above, I think there needs to be an ability to cut away the protection group & recovery plan without reinstalling the environment. From the looks at the other thread, that person will not be able to forcefully remove the protection group. SRM should not allow the SRA to interfere with the integrity & protection of the rest of the environment, particularly where there could be other array models involved. This is an Achilles Heel from an architecture standpoint.
Thank you,
Jas