Rebuilt server
-
Hi there, any help appreciated.
I have built a server to be used as the new prod SQL server. For all the apps to still work without having to change connection information I have to use the same server name IP address etc. It is a 2 node active/active cluster running SQL2000
Obv the servers can not be on at the same time as they will have the same name and IP.
So the plan is to backup all the dbs to tape (including system db's) restore to the new server (currently has a different name) detach all db's, reinstall SQL with the proper name and IP's and then attach the db's.
There are a lot of jobs and DTS packages that need to come over with the db's hence restoring the system dbs as well.
Anyone have an easier way to do this?
-
Some of this depends on how you are accessing your SQL Server accross the network. I would recommend looking into using DNS for the cutover. If you are referencing the server by host name instead of IP, DNS will make this easier as all you have to do is change the DNS entry at the time of cut over.
If you are using hard coded IP addresses, you may want to consider changing to host names.
-
Hi,
There are few points to consider before
Please refer to the following luinks for more information:
http://support.microsoft.com/kb/314546/en-us
http://support.microsoft.com/kb/224071/en-us
Minaz Amin
"More Green More Oxygen !! Plant a tree today"
-
Well I did it pretty much the way I outlined above, having the same server name was a pain.
The new server was patched with SP4 where the old one was sp3
so the system db's could not be restored. I have to transfer all the logins, jobs and packages to a test server and then transfer them to the new prod servers.What a pain in the butt.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply