October 18, 2004 at 4:19 pm
This hopefully is a simple question.
I have started log shipping from our production server to a server at another site.
The theory being it we have a disaster at one site we can bring up the server at the second site with minimal data loss. We are ok with being 15 minutes behind.
I wanted to simulate a disaster with one of our test databases that I have started log shipping with. Assuming the primary shipping database is no longer available. Lets say the primary computer room is under 10 feet of water. (just a scenario).
First question. How would I take the secondary database that is receiving the log files out of warm standby mode.
Second Question: I know there is Microsoft documentation for moving the database users assuming you can reach the primary database server. How would you keep the secondary database users current on a regular database if you could not reach the primary database server?
Thanks
David Weil
October 18, 2004 at 4:29 pm
1.
RESTORE DATABASE database_name WITH RECOVERY
EXEC SP_DBOPTION 'database_name', 'read only', 'false'
EXEC SP_DBOPTION 'database_name', 'dbo use only', 'false'
2. Search for sp_help_revlogins
October 18, 2004 at 9:47 pm
For the logins, you could do a BCP out of the syslogins table on a nightly basis and copy the output file to the second server. As part of our Distaster Recovery, we bcp out a view of syslogins other than the standard system logins (such as sa). Then, you could BCP them in when you need them. BCP allows you to keep the encrypted passwords the same.
Danette
October 19, 2004 at 6:49 am
2000 or 7.0?
October 19, 2004 at 8:48 am
2000
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply