April 21, 2005 at 4:24 am
Hi,
This is my first post as normally I can find something that helps here straight-away.
Right, on Monday a SAN failure took out our production box so we renamed a dev box to have the production box name using sp_dropserver/ sp_addserver. this worked fine and after a few restores/ login changes we have been chugging away without any issues.
Ok, the SAN has been fixed and the cluster server is available again. Obviously I need to reverse this process and ideally I'd grab a little data - post backup that will be in the failed production databases and apply this to some of our working databases before we think about bringing production back on to the network.
Now, what I'd like to do is simply remotely connect to this server box and use query analyser to get some data out. Problem is - now the DEV box has the server name of the production box how can I register/ query the production box itself?
Has anyone had this issue before? I'd assume I could detach the production box from the network and then register a local instance of SQL server. Is this just "(local)"? I can't find the server name of the old production box and if I register its old name it registers the dev box.
Also, when we get the data out whats the reverse process? I'd assume we'd rename the DEV box back to its original name, sp_dropserver/ sp_addserver and apply its latest database back-ups back to the Production box. Would the Production box then automatically assume its old name when brought back on line or is there something else we'd have to do?
Thanks in advance for your thoughts.
Cheers
Mark
April 21, 2005 at 5:18 am
Register your servers using ip address.
We tried re-naming a physical cluster , yes I know ms don't recommend it, and we had about a 50% success rate - so I wouldn't really recommend this. The servers got in an awful mess ( we renamed 4 clusters - swapping pairs of clusters in and out ) and it was very tricky to know which server was which.
Notwithstanding you can name the sql server to anything you like with the drop and add, but names need to be unique - so in a mess register with ip and give a unique name.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
April 21, 2005 at 5:21 am
Another way to accomplish this (Don't know if you have the capability) is to connect the OLD production system to a DIFFERENT DOMAIN and ensure that the two are NOT TRUSTED with each other. You will then need to have access to the other domain to grab data and perform analysis.
Good Hunting!
AJ Ahrens
webmaster@kritter.net
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply