Replace production server - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

Replace production server

Author

Topic

CanadaDBA

583 Posts

Posted - 2005-03-18 : 10:08:34

We are going to replace our production old server with new one. About two weeks ago, I setup the new server by detach/attach the system and user databases on the new server. Also, forced the new server’s name to the SQL-Server. Then Testers test the applications and everything was fine.
In coming weekend I am going to replace the servers. Here is the plan:
1. Get backup from all user databases
2. Move the BAK files into new server
3. Replace the old box by new box
4. Restore BAK files on the new server
By using this approach, do I miss something?
The new server will have new name but same IP. We didn’t have any table update or DTS/Job change. Do you think it is better to use detach/attach approach again? Is there any risk involved?

Canada DBA

JimL
SQL Slinging Yak Ranger

1537 Posts

Posted - 2005-03-18 : 10:19:07

Potential problem "The new server will have new name but same IP."

Your front end applications may not resolve to the new name.

Jim
Users <> Logic

CanadaDBA

583 Posts

Posted - 2005-03-18 : 13:09:32

We tested the applications when I setup the new server and set the SQL-Server with new machine name. There was no problem.

quote:
Originally posted by JimL

Potential problem "The new server will have new name but same IP."

Your front end applications may not resolve to the new name.

Jim
Users <> Logic

Canada DBA

bakerjon
Posting Yak Master

145 Posts

Posted - 2005-03-19 : 15:53:37

I believe it's not the name that was the issue, but the fact that the IP could cause issues, since it was tied to the old name. If DNS is updated it probably won't be a problem, but I would either take it out of the mix by using a new IP, or continue to use the same IP/Name combination.

Alternately, if the databases aren't big, you could take a different approach.
Install SQL Server on new machine in same path as old machine with same patches and SPs
Stop SQL Server on old machine
Stop SQL Server on new machine
Copy all databases (user and system) from old machine to new machine in same path
Start SQL Server on new machine
SQL Server will see the databases and keep on working
Logon to SQL Server and run sp_dropserver 'old_server_name'
Run sp_addserver 'new_server_name', 'local' (just like renaming server)

This is the "Cold Backup" approach. It is harder if the databases are large, because it takes a long time to copy over the network. It can work well, also if you have a SAN and can snap the volume to the new machine.

If the databases are large, you could do a backup and restore to the new machine and apply tran logs throughout the day from old to new. When it's time to cut over, just apply the last tran log to the new machine and rename or point the apps. This makes the cutover very short.

HTH

Jon Baker

quote:
Originally posted by farhadr

We tested the applications when I setup the new server and set the SQL-Server with new machine name. There was no problem.

quote:
Originally posted by JimL

Potential problem "The new server will have new name but same IP."

Your front end applications may not resolve to the new name.

Jim
Users <> Logic

Canada DBA

What's with the yak thing?

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources