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.
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....
zgz_rever
1 Rookie
•
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
2 Intern
•
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....