February 4, 2011 at 3:37 am
Hi there
We have a fairly standard DR setup here in that we have warm standby servers at a separate location and we use log shipping to keep the SQL boxes in synch and various other methods for Exchange, AD etc.
Once a year we have a 3-day DR test whereby we cut our links to the remote site and recover all the servers. The recovery site isn't used as live but purely to prove the recovery process. Some business personnel arrive on day 2 and sign off that the systems work as expected. Day 3 is used for troubleshooting and updating of recovery processes.
The issue is that for those 3 days we are effectvely without a DR capability and no way of copying data offsite quickly. I was wondering how other companies managed this risk. A fairly basic option is to move the test to a weekend which would cut our data risk consderably. Another option, certainly as far as log shipping is concerned, is to have 3rd site where we could simply dump our transaction logs for those 3 days - some sort of mass storage area where at least we have a copy of the data.
Any thoughts on this subject are welcome.
cheers
February 4, 2011 at 6:38 am
The company I used to work for did that annually. They would only take the backup process offline on a weekend, so all the prep was done and then testing was over a two day period. I never did it personally, but I heard it was quite the adventure.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply