July 6, 2009 at 9:57 am
We are going to upgrade an active 32 bit sql 2005 cluster to a 64 bit OS and SQL Server. I am looking for pitfalls for anyone who has done this. This is a mission critical server. The db's are on a SAN Here is my current plan
1.Remove passive node from cluster
2.Rebuild this with 64 bit OS and sql server 2005 64 bit
3.Deattach the production databases and copy to share?
4.Script out all logins and jobs
5.Blow away production active box, add former passive server as new active server and reverse steps 3 and 4.
6.Rebuild former active box to 64 bit and add to cluster
My main question is, can I just deattach all the db's including master and msdb or will this not work?
July 6, 2009 at 10:47 am
master and msdb cannot be detached, they are required for system use.. You *might* be able to do a db backup then restore of master and msdb. But you will need to update the servername in the server using sp_addserver (be sure to specify the LOCAL option) and sp_dropserver. I don't think there is really any difference in master/msdb for 32/64 server. Restoring master is always a little painful, if you haven't done it before look it up in BOL..
I'm sure if I am mistaken others will correct.
CEWII
July 6, 2009 at 10:55 am
You can't restore the system databases - and you shouldn't need to. Once the x64 cluster is up, then it should be no problem for you to create the jobs (script on old, execute script on new) and script the logins.
You shouldn't have any user objects in master anyways, so that should not be an issue.
The only thing that could make things a bit easier/faster for you would be:
1) Define the same LUN's on new system and set them up in the cluster
2) Perform a cluster recovery for the LUN's on the old system to the new system
a) this should 'move' the LUN's to the new system
3) Attach the database to the new system
Check with your SAN vendor on the above procedure to make sure you have the exact steps needed to perform this. Worse case is that you un-present from old, present to new with same names.
This could save you quite a bit of time, depending on how large your databases are.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 6, 2009 at 11:19 am
Hi Tim,
The only thing you need to worry about the Master and MSDB databases is whether you have any user created stored procedures in those databases.You can script those stored procs and you can re-create them on the new server.
If you want to move the system databases check this link:
http://msdn.microsoft.com/en-us/library/ms345408(SQL.90).aspx
Thanks
Best Regards,
SQLBuddy
July 6, 2009 at 12:12 pm
Everything will be staying in the same place, db's log files etc. If we can restore master and msdb I am in great shape
July 6, 2009 at 1:44 pm
we did this, but with all new hardware
first we built the new x64 cluster
uninstall SQL from the x86 cluster
install SQL on new cluster
attach databases
recreate jobs, we usually use a staging server with the same db names to hold the jobs. or just script out the jobs and recreate from script
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply