It is a little difficult to grasp, but the documentation seems to suggest that I should be able to break an SVM-DR relationship, and rehost a destination DR volume. Of course there are other steps, such as, setting source volume svm-dr-protection to unprotected, running and SVM-DR update, breaking the SVM-DR, and releasing -info-only.
I still cannot rehost the destination volume because it belongs to a type DP SVM.
There is one additional step, which is to online the destination SVM, but I am afraid to do that, because this is a rather large SVM and I don't want to lose the baselinel.
The SVM's have about three hundred volumes, which I need to re-host to another SVM which will keep them for the longer term. I will not need any further updates from source, because the source volumes will be deleted.
Can anyone shed any light?
BTW, I can't open a call with Support, because the DB is apparently messed up, and they are in process of recovery.
#Re-hosting destination volumes in an SVM-DR relationship
random hare
ashen eagle
did you try simply creating a FlexClone of the destination volume?
random hare
FlexClone works, but I want to get the volumes out of the SVM without copying. I have about 5PB of data in this SVM-DR.
However, I think I may be able to do it, if I start the destination SVM; of course I will need to shut down the network so it does not try to take-over; then I can, perhaps, rehost and restart the network and stop the destination SVM. Of course, I'm trying to get some assurance I will not lose that data... 😉