We had a line break between our primary and secondary ONTAP systems where we have mirrorvault relationships... the SnapCenter jobs of cause fails as is was unable to update the mirrorvault, but the local snapshots were created OK... only thing is that it didn't tag a snapmirror label on those snapshots 😦 So now we have resynced the mirror now, without knowing this fact, and of cause have a "hole" in our backup snapshots... I will now try to manually lable these snapshots and resync the relations, but I doubt it will work?
#SnapCenter for vSphere issues when mirrorvault is disconnected...
1 messages · Page 1 of 1 (latest)
...my workaround so far is to add the "daily" snapmirror label to the snapshots on the primary side... then I have to do snapmirror updates for each missed snapshot, one at a time... would be nice if this could somehow be automated, or snapcenter could just add the snapmirror labels regardless the snapmirror update status... seems odd to me that it is not set, because you would have to set it, and then try the snapmirror update... this would then have failed... but I guess they just removed the snapmirror label again after it failed, or they do it in some other day?
I've given this idea to the development team for SCV. Thanks for the feedback.