Restoring anothers Server's System Database

[jimmYLepp]

I work at a remote location where I locally support central developed systems. Currently, I am testing the fail over for one of the systems. The biggest portions of this fail over is restoring the SQL Server Databases from the Primary Server to the Backup Server. The central office folk want me to restore the system databases msdb and master, now I know this is not a great idea but I have to follow their instructions or I get blamed for anything going wrong. What I need to know is there any tables in the system databases that need to have modification because they are now on a new server. An example would be, in the sysservers table in the master database only has entries for the Primary Server instead of the Backup.

jimmY

 

[SemperFiDownUnda]

ok....here is what you should do. When you goto restore, restore everything but one of the steps to bringing up a backup server of this kind is that the primary server is removed from the network and the backup server is renamed (and possibly IP address changed) from this point the database should not have a problem being on a different box as the identity of the box is the same.

 

[jimmYLepp]

sounds good, but here is the problem, I don't want to change the backup server name. yes, i know it sounds foolish, but that's how they want it.

jimmY

 

[MaffewW]

maybe I misread... so in the event of a problem, they want to bring the backup server online but not have it renamed or allocated the same IP address as the old server?

 

[jimmYLepp]

yup, what they want is to change where we are getting the inputs to the backup server and then point the web page (system output) to the new server as well.

Later jimmY