Migrating SQL 2

[WhoKilledKenny]

I have an Active/Active SQL 2000 Cluster (running on win 2003 Ent) that is being moved from an old SAN to a new SAN. All hardware has been tested; each cluster node sees the old and new drives, new drives have been added as Disk Resources in each SQL resource group. Quorum and MSDTC move has been tested. What I am looking for is any documentation on proper guidelines for moving SQL Databases, including master.

I would like to move all data to new drive resource, and then remove the old drive resource from the cluster group. I am researching MS web-site for info. If you have any quick links or would like to share your experience, please do.

Thanks.

 

[mrdenny]

It's actually fairly easy to do.

Stop SQL
Copy the files to the new drive.
Remove the dependency from old drive to the SQL Server.
Change the drive letters.
Add the dependency back in.
Repeat for the other drives
Start SQL

What SAN vendor are you using? Some of them have software to make this even easier.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[WhoKilledKenny]

Yes,
You are right that would be easy. Let me give you more on the senario. This is our enterprise database server, meaning many large databases (accessed at different times of the day) that can't be moved at the same time.
The idea is to present the new disk resorce, make it a part of the SQL dependency, and move databases to new drives. So each database would be moved at different times - can't change drive letter.

With regards to you SAN question it's IBM. We have been down that road with them. Still, are requirment is that we can't move the databases at the same time. So that kills a one time migration solution.

 

[mrdenny]

If you are going to do it that way then.
Stop SQL
Make the SQL Server dependant on the new drives.
Detach each database one at a time and move it.

When it comes to the system databases I'd recommend using the method I described above. Changing the drive letter for the system databases is a pain at best.

If you happen to know anyone with an EMC SAN they have a peice of software called DRU which will copy the data from one disk to another live then once the data has been copied you reboot the machine, and the software automaticaly switches the drive letters for you.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[WhoKilledKenny]

Thanks for your replies.

When it comes to the system databases I'd recommend using the method I described above. Changing the drive letter for the system databases is a pain at best.

This is the issue our DBA has been not able to tackle on our test cluster.
I think I might test the addition of a separate disk resource for the system databases. Then test changing the Drive letter for the System database drive resource.

If you happen to know anyone with an EMC SAN they have a peice of software called DRU which will copy the data from one disk to another live then once the data has been copied you reboot the machine, and the software automaticaly switches the drive letters for you.

IBM also support a live migration tool, IT Management does not have faith that the records will be updated and synced. I can only go try to provide a solution that is acceptable with regards to risk.

Again thanks...

 

[mrdenny]

Assuming that the IBM software works the same way that the EMC software does the risk is very low.

The EMC software works like this.

First the software copies all the pages from the disk to the new drive. As data pages are changed they are simply written to both disks. Once all the static data pages are done the changing pages are simply written to both locations.

What problems has your DBA been having changing out the clustered drive letter?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[WhoKilledKenny]

[qoute]What problems has your DBA been having changing out the clustered drive letter? [/quote]
Well... He tried to change the path to the system databases in Enterprise Manager (that blew up). At least that is what I got out of him... (He is an oracle guy who inherited all of the SQL DBs).
I have been busy setting up cluster for your suggestion.

I will also be searching MS web-site for documentation on how to move sys DBs. Just haven't gotten to that yet.

If you have any links to what I need, please post.

 

[mrdenny]

Sorry, I don't have any links.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[mutley1]

Here's the KB on moving system databases.

http://support.microsoft.com/kb/224071/

Cheers,

M.

 

[WhoKilledKenny]

Thanks for the link mutley...