Changing Logical Drives in Windows - For SQL 2000 Cluster

Hi there,

I am helping perform a SAN move and basically need to "swap" drive letters (from disks on the OLD SAN to disks on the NEW SAN)... with all data having been actively replicated and mirrored, so that when I bring the "NEW" SAN disks online, they will have the same block-level contents as the "OLD" disk.

I need the feedback pretty urgently, I just want to make sure I am stepping through this properly.  I am familiar with this process, but it never hurts to write it out and ask! =)

I'm pretty sure this is a straightforward process, and wanted to get some feedback that my process is correct.

This is a Windows 2003 Server, running a SQL 2000 Cluster.  We are changing SAN's, so I need to bring the "NEW" disks online (using the SAME drive letters as the OLD SAN) and bring the cluster node back online.

Here is what I projected as requirements:

1.  Ensure all jobs and backups have completed on the SQL Databases, verify any DB Locks & clear them, goto to Cluster Admin and stop all SQL related Services, excluding any disk resources.

2.  In Cluster Administrator, take the source drives offline, and then delete the drive entries.

3.  With all disks being presented to BOTH nodes, start by reassigning the drive letters from the OLD disks away from the existing letters.

4.  Using Disk Management, start re-lettering the "NEW" SAN disks to match that of the OLD disks... (keeping in mind that data on the "NEW" disk is already replicated from the existing disk).

5.  Migrate the Quorum Disk (Q:) - ((I would guess it's best to move the quorum to a temporary location, and then to the final "new" disk once I have changed it's drive letter assignment, correct?))

a.  Start Cluster Administrator (CluAdmin.exe).
b.  Right-click the cluster name in the upper-left corner, and then click Properties.
c.  Click the Quorum tab.
d.  In the Quorum resource box, click a different disk resource.
e.  Choose the drive location for the quorum

4.  After re-lettering is complete, in Cluster Administrator, create a new cluster disk resource for the new drives and adjust dependencies for SQL Server.

5.  Bring the Disk Resource group online, to bring the new resources online.  After Disk Resource group has restarted successfully, bring the SQL Admin group online and verify no errors in the Event Logs.

6.  Open Enterprise Manager and verify that the Database is online and that there are no errors / and that all jobs are processing properly.

Does this sound correct?  Anything I should be looking at that I might be missing?

Thanks for the help everyone!!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Justin OwensITIL Problem ManagerCommented:
That sounds like a solid plan.  I would offer this word of caution.  Make sure your Windows servers don't sent an "initialize" command to the SAN (which it likes to do from time to time, especially in clustered mode).  That can result in data loss.  Learned that the hard way. :(

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ryan McCauleyEnterprise Analytics ManagerCommented:
I assume NTFS permissions are part of your current disk replication - make sure they are, because if they're not, the SQL Service can have trouble writing what it needs to.

Sounds like a good plan overall, though - has all the steps I'd think to include. I'm not sure how the cluster nodes will respond if you take the quorum disk offline though, so you always have the option of attaching an additional LUN, assigning it to the quorum group, and then telling the cluster to use the new drive as the quorum drive instead - that way, your Quorum stays online the whole time, and the cluster will just switch to the new drive. That will change your quorum drive letter though - if you'd prefer to keep it the same, just repeat the procedure again with a LUN on the new SAN, setting the new LUN to use the "old" quorum drive letter, and voila.

Good luck!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.