UNSOLVED
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?
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.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
847
0
Posted December 18th, 2013 06:00
have you considered using SANCopy or PowerPath Migration Enabler ? Win2k3 clusters use disk signatures, so simple drive letter swap will not be sufficient.