Guys,
Please be aware that MSCS will keep track of the lun serials. So you would probably need to set the lun serial numbers back to the original ones when your snapmirroring to another filer.
Regards,
Patrick van Helden
Databasement BV
pvh@databasement.eu
-----Oorspronkelijk bericht-----
Van: owner-toasters@mathworks.com namens Milazzo Giacomo
Verzonden: vr 5/16/2008 18:01
Aan: Klise, Steve; toasters@mathworks.com
Onderwerp: R: MSCS and snapmirror question
You will not have issues. And you don't need to update your mirror.
If you simply power off you clusters no i/o activity will be performer on LUNs. Then you can simply copy (vol copy) the volume(s) containing your LUNs, rename the new volumes as the old (in case of iSCSI LUNs and if you don't want to recreate the connections) and restart you clusters.
In case your nodes (but it will not happen) will loose the LUNs with Snapdrive you can safely reconnect them starting with the quorum one, on first node then restarting the cluster service, then on the second node and so on with all other cluster shared LUNs
Regards
-----Messaggio originale-----
Da: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Per conto di Klise, Steve
Inviato: venerd́ 16 maggio 2008 15.50
A: toasters@mathworks.com
Oggetto: MSCS and snapmirror question
I am migrating from an aggregate to another aggregate in the same filer (6030). The LUNS are attached to print clusters, 2 node and 3 node clusters (WIndows 2003 sp2 x86 etc).
I have snapmirrored the volumes. If I stop the cluster service on the windows boxes, do a snapmirror update, the disconnected the quorum and other resource disks, do a snapmirror update, release the snapmirror, remove and replace the disks with snapdrive with the same disk letters. fire up the cluster service.. Will that work? has anyone done that before? Any gotchas?
Any help is greatly appreciate!