Move SQL 2000 to replacement Server
-
Novice SQL user given project to replace current SQL server with the Disaster Recovery(DR) machine to facilitate complete rebuild of original machine (new drives, processors and array configuration). The DR server will have IP and name of current SQL server during its life in the domain. Once rebuilt the original SQL server will be reintegrated into the domain and the DR server removed. The DR server has SQL installed and is running the databases and software required. I've read up on various articles on using Detach/Attach and moving by restoring but understand that as the name of the DR machine will change I will need to delete and re-register the SQL Server.
Does anyone have any words of wisdom, caution or even a recommended order to carry out this task!
Any help would be much appreciated.
Thanks
-
Is this you are looking for?
When you change the name of the computer that is running Microsoft® SQL Server™ 2000, the new name is recognized during SQL Server startup. You do not have to run Setup again to reset the computer name.
You can connect to SQL Server using the new computer name after you have restarted the server. However, to correct the sysservers system table, you should manually run these procedures:
sp_dropserver old_name
GO
sp_addserver new_name, local
GO
When you have more than one instance of SQL Server on the computer, change the sysservers system table information by running the stored procedures this way:
sp_dropserver old_servername\instancename
GO
sp_addserver new_servername\instancename, local
GO
-
We do this all the time for EOL servers and use the method that Allen mentioned. We perform the following:
1. Run full backup from source machine, restore on new machine. Leave DBs in loading state (norecovery option)
2. Notify users the server is going down.
3. Run diff backups on source machine, load on new machine. Dbs in active state
4. Rename old machine, namexxx_old, reboot
5. Rename new machine.
6. Run Allens' script above and reboot new machine.
7. If the new machine is taking over the IP (not always), we change the IP on both machines. If not, we verify updates in DNS/Wins
Steve Jones
http://qa.sqlservercentral.com/columnists/sjones
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com -
Thank you for the prompt reply. I've searched for hours trying to find a simple explanation of what to do. Its nice to know you can find one here. I'm going to have a try on the DR server and then take things from there. Thanks again to you both
-
quote:
We do this all the time for EOL servers and use the method that Allen mentioned. We perform the following:1. Run full backup from source machine, restore on new machine. Leave DBs in loading state (norecovery option)
2. Notify users the server is going down.
3. Run diff backups on source machine, load on new machine. Dbs in active state
4. Rename old machine, namexxx_old, reboot
5. Rename new machine.
6. Run Allens' script above and reboot new machine.
7. If the new machine is taking over the IP (not always), we change the IP on both machines. If not, we verify updates in DNS/Wins
Steve Jones
http://qa.sqlservercentral.com/columnists/sjones
Steve:
Is this done for all databases i mean master,msdb, userdb1, userdb2 ...etc ?
What if replication was running on the original server and you had the distribution database on it ?
thanks
-srini
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply