We used to have the destination DR setup with no production vLANs on the ifgrp's. Now they've been added, and an online DR SVM brought its LIFs up, causing a collision. I did a quick searcch in the CMD guide, but not sure how to prevent that from happening. Can anyone point to a specific SVM-DR guide on how the destinations should be setup when in SM/SV mode?
#SVM-DR destination bringing up LIFs
fleet venture
sudden nexus
when you create SVM-DR and use preserve identity you will have on the target System an relationship that has an Source_SVM: as sorce and a Source_SVM_DR as target on the target system ; the _DR SVM is off (stopped ) and you can not start it until you have broken the SVM relationship ( quesce and break or you can activate target but in this case the source SVM should be stopped ) lifs are showing up/down and SVM that is _DR has the state dp-destination ; you can not have both source and destination SVM lifs up when the snapmirror relationship is on !!! ( if you do have this and it is SVM-DR then it is not with identity preserve "‑identity‑preserve true" and it should be ...) https://docs.netapp.com/us-en/ontap/data-protection/snapmirror-svm-replication-concept.html#xdp-replaces-dp-as-the-svm-replication-default-in-ontap-9-4
sudden nexus
i will post a link that shows you how to test this in a proper way : https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Guidelines_for_SnapMirror_Disaster_Recovery_DR_testing_and_reverse_SnapMirror_in_ONTAP
fleet venture
Thank you Alex; I will have to read up, because we had the issue you described that we should not have had. I'll post any further findings after reading the document./