DR Merge Master DB''s
-
Here's the deal.
At our production site we have two SQL servers (call them SQL1 and SQL2) that have completely different DB's and primary functions. The paths to the databases are slightly different betwen the two servers, but both reside on the D: drives . At our recovery site we have one sql server (call it SQLR).
We have, recently, setup SAN replication on a daily basis that gets replicated to the DR site. It copies all the data -- including the SQL Server DB's on the LUN's. At the DR site we can mount "time marks" of the volumes onto the SQLR server as if they were the original drives. Then fire up the SQL server as if it was the original server.
We just realized that we'll only have master DB/instance of SQL running.
This is where our nightmare is that the DB's are on one server or the other. (Hey, I said recently as in the past 30 days. 
) Does anyone else have this problem? And how do you get around it? Can we somehow restore the other master and import it into the original? Any other ideas?
We have a DR test coming up in less than thirty days. And this will be the first time going through this with the SAN.
Our old recovery was from tape.
----------------
Jim P.A little bit of this and a little byte of that can cause bloatware.
-
This was removed by the editor as SPAM
-
The location of master is a parameter in the service startup. At the DR site, setup the startup parameter with a different master. Then when it comes up, you'll need to move msdb (http://qa.sqlservercentral.com/columnists/sjones/movingmsdb.asp). Also tempdb (http://qa.sqlservercentral.com/columnists/sjones/atemporarymove.asp)
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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply