2 Iron

Windows 2003 cluster - MS SQL Server 2000

We have an active/passive Windows 2003 cluster running SQL Server 2000.  We have LUNs allocated that serve as quarum, data, logs, and backups.  This is currently FC attached to an existing CX500.

We have since migrated to a VNX 5700.  I have created new LUNs to replace the current allocated LUNs.  My goal was to assign the LUNs to the storage group that contains both server nodes.  Can it be as simple as doing a copy locally from disk LUN to disk LUN, then simply give the new LUNs the same drive letters as the previous LUNs?  Would anything in clustering and cluster resources get fouled up here?

0 Kudos
8 Replies
7 Thorium

Re: Windows 2003 cluster - MS SQL Server 2000

have you considered using SANCopy or PowerPath Migration Enabler ?  Win2k3 clusters use disk signatures, so simple drive letter swap will not be sufficient.

0 Kudos
2 Iron

Re: Windows 2003 cluster - MS SQL Server 2000

Could you please elaborate on the proper path to using either SANCopy here or PowerPath Migration Enabler?

0 Kudos
7 Thorium

Re: Windows 2003 cluster - MS SQL Server 2000

1)  Do you have SANCopy installed on CX500 or VNX ?

2) What version of PowerPath are you using ?

0 Kudos
2 Iron

Re: Windows 2003 cluster - MS SQL Server 2000

I do have SANCopy installed on both.  I did find the PP Migration Enabler under PP 5.7 SP1.  To which is deemed the easier path?  I seem to be leaning towards PPME now.

0 Kudos
7 Thorium

Re: Windows 2003 cluster - MS SQL Server 2000

PPME is awesome, download the guide ..they have good examples. If you are willing to sacrifice some CPU  (very negligible) and not in a huge hurry, i would chose PPME.

0 Kudos
3 Argentum

Re: Windows 2003 cluster - MS SQL Server 2000

Alternatively use Open Migrator for Windows. Thats a pretty cool tool as well.

0 Kudos
7 Thorium

Re: Windows 2003 cluster - MS SQL Server 2000

wouldn't OM require reboot to install it and then to commit the session ? Any restrictions in MSCS  environment ?

0 Kudos
3 Argentum

Re: Windows 2003 cluster - MS SQL Server 2000

OM does require a reboot sometimes during the attach of the filter driver to the volume/s. Although the documentation does reocmmend to reboot the server. Depends on the state of the volume and whether any exclusive locks on it.

From a cluster perspective, OM 3.12 adds cluster target resources in the Cluster Groups, and requires all nodes in the cluster to be online during the commit.

0 Kudos