Ryan wrote: Hi Jason, It sounds like it's failing in the section of code I suspected then. Feel free to continue working with Lee on this and sending him whatever logs/screenshots you hav...
See more...
Ryan wrote: Hi Jason, It sounds like it's failing in the section of code I suspected then. Feel free to continue working with Lee on this and sending him whatever logs/screenshots you have as I can get them from him if an SR can't be filed. I'm curious about a couple things when the group is in this state and just want some confirmation. If you get a chance and don't mind trying some things out upon reproducing this then can you answer the following for me: 1) Can you edit the recovery plan to remove the group? I think the plan may be in the Incomplete Reprotect state and it should allow editing. (Maybe you addressed this already in your original post.) This would allow other groups to proceed with reprotect. Otherwise creating a new plan with working groups may be another option. 2) Can you unprotect VMs from the group in the "Protection Group" "Virtual Machines" tab? This shoud be enabled. If so then does it work? If you remove all the VMs in the group and then run Reprotect again does it now work? (Given where it's failing I suspect it won't work, but it's worth a shot.) 3) Is the ability to remove the protection group just not available when it's in this state? I suspect it may be given our UI specification. Otherwise, if it is actually available then with what error does it fail when invoked? Thanks, -Ryan As luck would have it, I wasn't able to reproduce the problem earlier this morning for 2 hours, then this afternoon it showed up in a live customer demo Reprotect and Reprotect with Force Cleanup does not complete; instantly fails. This time due to step 1.0/1.1 failing "Error - Failed to reverse replication for failed over devices. Cannot process device '21666' with role 'target' when expected device with role 'promotedTarget'." 1) Yes. After I remove the PG, the RP goes into an error state about "This plan cannot be run because it doesn not contain any protection groups.". On the PG side, the PG is still in "Reprotecting..." state & it cannot be edited or deleted. I then ran a Reprotect against the Protection Group after the VMs were removed from the PG individually. This resulted in an immediate failure as did the Force Cleanup option. 2) Yes.I can remove all VMs from the protection group. Then at that point, the PG still exists in a "Reprotecting..." state and cannot be edited or deleted. 3) I've only seen the inability to remove the PG when it's hung in the "Reprotecting..." state. Screenshots and logs sent to Lee Dilworth via FTP/email followup. Thank you, Jas Message was edited by: jasonboche Added additional step/reponse to 1)