Add SAN Disk Resource to Active/Active SQL cluster

Looking to see if I am missing any steps below to adding a SAN disk
resource to an Active/Active SQL cluster:
-Create Volumes
-Present LUNs to both Nodes
-Failover Cluster Groups to Node2
-On Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node1
Rescan for hardware changes
Write the disk signature
Set disk to basic
Create Partition
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node1
-On Node2
Failover Cluster Groups to Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node2
Rescan for hardware changes
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node2
-Assign disk resource to Cluster Groups
-On Node1
Take SQL Server Resource offline
Add SQL Server Resource dependency to disk resource
Bring SQL Server Resource online
-On Node2
Repeat above
-Test failover
Thanks,
Ian in SD
With Windows 2003 as the host, you may be able to skip some of the reboots.
You can rescan the disk list and pick up newly added disks. I have never
had to disable or stop the cluster service to pick up new disks. I do make
sure and do all the work on a node that does not currently host any cluster
resources. Once I am done, I can rescan the disk list on the other node(s)
and failover at will. If you have the downtime, the reboots won't hurt, but
they may not be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<theredmiata@.hotmail.com> wrote in message
news:1142967852.423752.294080@.i39g2000cwa.googlegr oups.com...
> Looking to see if I am missing any steps below to adding a SAN disk
> resource to an Active/Active SQL cluster:
>
> -Create Volumes
> -Present LUNs to both Nodes
> -Failover Cluster Groups to Node2
> -On Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node1
> Rescan for hardware changes
> Write the disk signature
> Set disk to basic
> Create Partition
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node1
> -On Node2
> Failover Cluster Groups to Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node2
> Rescan for hardware changes
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node2
> -Assign disk resource to Cluster Groups
> -On Node1
> Take SQL Server Resource offline
> Add SQL Server Resource dependency to disk resource
> Bring SQL Server Resource online
> -On Node2
> Repeat above
> -Test failover
> Thanks,
> Ian in SD
>
|||Thanks for the reply Geoff. This the first time for this process as we
are trying to split the file groups and would like to have each group
on a seperate volume.