This post is more than 5 years old
53 Posts
0
4616
Suspended distributed device
Hi
I have a problem with a distributed device in VPLEX. If I check the status of the Distributed Device in the CLI it says:
summary:: suspended, details:: [requires-resume-at-loser]
However, when I execute "resume-at-loser", I get the following output:
consistency-group resume-at-loser: Evaluation of < > failed.
cause: Failed to resume I/O at cluster cluster-X in consistency-group 'XXX'.
cause: Firmware command error.
cause: Property is not awaiting resume.
Can anyone help me please?
Thanks
zgz_rever
53 Posts
0
June 27th, 2012 05:00
Found the solution!
Even though the consistency groups are distributed across both clusters, they are always created in one of them. The cosistency group must be "resume-at-lose r" in the cluster where the consistency group was created. Stupid behavior but that is the only way to make it work.
I hope I help someone in the future
Menno
29 Posts
0
August 30th, 2012 08:00
Distributed devices wil also go suspend in à consistency group if you powerdown one cluster in à metro config. When is involved and i/o gets to the "winning" cluster, you have to manual do the resume at loser command....
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
February 8th, 2013 06:00
I have a customer that has the VPLEX 5.0 Geo and has been testing failing components to see how their servers respond. The setting we see to control the Consistency Groups is the ‘auto-resume-at-loser=true’. We realized that needed to be set or we had to manually bring the CG's back online.
Is that the recommended setting? Is there a "bring all CG's online" command?
Would you recommend setting this to true for VM as well as SQL?
Thank you!