Re: Cluster Disk re-config

Once you create a new physical disk resource in the cluster admin you can change your quorum drive. I did not fuss around with copying the MSCS folder.

Follow this guidance I used when I moved to a new SAN. You're going to be doing a similar process to move the quorum even though you are on the same SAN:

http://msmvps.com/blogs/clusterhelp/archive/2005/08/05/moving-a-cluster-to-a-new-san-original-posted-jul-22-2005.aspx

Moving a Cluster to a New SAN - Original Posted Jul 22, 2005
A fairly common scenario for a cluster administrator is to move a cluster from one SAN to another as SAN equipment is replaced with newer/faster SANs or the old SAN's lease is up and a new one is being brought in.

The easiest way that I have found to do this is to use these steps (this is from memory, let me know if I missed one or two):

Super High Level Steps:
1. Put the new array in the same fabric as the existing array
2. Create new LUNs on the new array and make sure they are visible to the nodes
3. Map the new LUNs to the old drive letters
4. Copy data from the old drive to the new drive
5. Move quorum and MSDTC
Slightly More Detailed Steps:
1. Carve the new LUNs on the new array
2. Add the new array and its LUNs to the same switch as the existing array
3. Configure the LUN masking on the switch to expose the new LUNs to NodeA and NodeB
4. Use the disk management tools in Windows to rescan the drives
5. Use the active node to partition and format the disks
6. Use Cluster Administrtor to create the new physical disk resources and put them into their proper cluster groups
7. Move the Quorum using the GUI to a temp location
1. In Cluster Administrator, right click the cluster name
2. Select Properties
3. Select the Quorum tab
4. Use the drop down box to select a temp location for the quorum
8. Delete the existing MSDTC folder (if any)
1. Stop the MSDTC resource
2. Copy the MSDTC folder from Q: to the final qurom disk target location
3. Stop the Q: resource (remember, the quorum isn't there anymore)
4. Delete the MSDTC resource
9. Move the quorum to its final location
1. Go into disk management and change the Q: name to another letter
2. Use disk management and name the final quorum drive to Q:
3. Repeat steps 7.1-7.4 to move the quorum to its final destination
10. Recreate the MSDTC resource
1. Create a new MSDTC resource with the clustername network name resource and the new Q: as dependencies
2. Bring the MSDTC resource online
11. Stop the cluster service and the application cluster groups (you can just stop the application resources if you want to move app data an app at a time)
12. Move the data from the old disks to the new ones
13. 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
14. 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)
15. Verify that all dependent resources are pointing to the proper physical disk resource.
16. Restart the cluster service
17. Make sure the new drive letters and disk resources are showing up properly in cluster administrator
18. Bring everything back online
Again, these are basic steps. Some of the individual steps will require lots of work. I have done this now several times and am very happy with the results.
Published Friday, August 05, 2005 7:14 AM by cluster
Filed under: Storage Area Network
Comments
No Comments



gjb wrote:
Hi,

I need to reconfigure my disk/LUN distribution on a SAN which hosts the shared disks for 2 clusters and am hoping someone with somewhat more experience could provide some guidance.
The intention is to add additional storage,config the new LUNs/ Shared disks, move all existing data to the new disks and then destroy and reconf the old storage before moving some data (Oracle DB) back.
The process looks fairly straightforward except that 2 of the existing disk groups contain the Quorum disks (Q:).
I am unsure as to the best approach. I think this would work but mayb e there is a better/easier approach:-
- Create new LUNS with different drive letters and just use CLUADMIN to redirect the quorums, reconf SAN, create new LUNS for quorum using the now available Q: letter and move Quorumj back to Q: in CLUADMIN again.

(The SAN is Dell/EMC CX300)

Many Thanks,

Geejay.


.

Relevant Pages

  • Re: Split brain scenario in cluster server system
    ... Whenever the cluster cannot determine who owns the quorum, ... Eachnode in the cluster renews the disk reservation that it owns, ... tries to reserve the quorum disk. ...
    (microsoft.public.windows.server.clustering)
  • Re: Clustering Newbie - SAN Advice
    ... You are right to observe that we probably don't want cost of full-blown SAN ... piggy backing them on some sort of shared disk array. ... The disks in the array doesn't need anything special. ... single-instance cluster. ...
    (microsoft.public.sqlserver.clustering)
  • RE: Move quorum to new disk
    ... The procedure for actually replacing the quorum disk is identical to ... required to startup the cluster in the event of a quorum disk failure. ... replacement procedure outlined in Recovering a shared disk to replace the ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... yeta lot of times it depends on each customer's enviornment and the complexity of the SAN migration. ... 305793 How to Replace a Disk That Is on a Windows 2000 or a Windows 2003 Server ... Windows NT/2000/2003 Cluster Technologies ... >> 4) Create a new Disk Resource for the new disk and have that in the SQL ...
    (microsoft.public.windows.server.clustering)
  • Re: active active windows 2003 clustering
    ... >>create the cluster, ... During Windows 2003 MSCS analysis the Quorum ... Disk selection process follows Best Practices ... >>cluster install on windpws 2003 server enterprise. ...
    (microsoft.public.windows.server.clustering)