Migrating Windows SAN Clusters
12:06 PM- Carve the new LUNs on the new array (Storage)
- If possible, add the new array and its LUNs to the same switch as the existing array (Storage).
- Configure the switch to expose the new LUNs to NodeA and NodeB (Storage)
- Install Powerpath/Multipath and then use disk management to rescan the drives
- Use the active node to partition and format the disks
- Use Cluster Admin to create the new physical disk resources and put them into their proper cluster groups
- Move the Quorum using a temp location
- In Cluster Administrator, right click the cluster name
- Select Properties
- Select the Quorum tab
- Use the drop down box to select a temp location for the quorum
- Delete the existing MSDTC folder
- Stop the MSDTC resource
- Copy the MSDTC folder from Q: to the final qurom disk target location
- Stop the Q: resource
- Delete the MSDTC resource
- Move the quorum to its final location
- Go into disk management and change the Q: name to another letter
- Use disk management and name the final quorum drive to Q:
- Repeat steps 7.1-7.4 to move the quorum to its final destination
- Recreate the MSDTC resource
- Create a new MSDTC resource with the cluster name network name resource and the new Q: as dependencies
- Bring the MSDTC resource online
- Stop the cluster service and the application cluster groups (you can just stop the application resources if you want to move app data one at a time)
- Move the data from the old disks to the new ones
- Re-letter the old disks to something outside the current range, but do not remove them yet - you might need to use them in your back out plan
- Re-letter the new disks to the same drive letter as the old ones (no, you do not have to worry about disk signatures as applications don't understand disk signatures and don't care about anything other than drive letters)
- Verify that all dependent resources are pointing to the proper physical disk resource.
- Restart the cluster service
- Make sure the new drive letters and disk resources are showing up properly in cluster administrator
- Bring everything back online
0 comments