August 30, 2010 at 4:40 am
We currently have got the necessary servers ready to build a cold standy-by DR for our current production environment. The DR SQL database is expected to be synched once in a day with the production database. Hence we wanted to check with you if you have any standard practices / documents that you could share with us to understand:
1. The steps to be taken / be prepared for when we need to bring the DR site up when have a catastrophic failure in the current production environment
2. The steps to be taken / be prepared for when we need to promote the failed production environment back to production by pushing across the data held by the DR environment database while the DR site was promoted to temp production when the primary site was down.
Please mail me : abhishek_dwivedi03@infosys.com TIA 😀
August 30, 2010 at 5:23 am
Actually it depends, what exactly your customers requirement is.....
because from budget to latency and dataloss it depends.
But I guess budget is low and latency will be fine from your description. You can consider Snapshot replication if the database size is very small or you can think of Log Shipping, mirroring etc.
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
August 30, 2010 at 8:54 am
Hi Srinath,
As you need once in a day day referesh, it would be better to use Log Shipping which a very robust and proven solution for the DR.
If you need realtime data synchronization, use Database Mirroring.
In both the cases you can do the Manual/Automatic Failover (DB Mirroring) to switch back to the actual prod server from the DR server.
http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx
http://www.sql-server-performance.com/articles/clustering/mirroring_2005_p1.aspx
Thank You,
Best Regards,
SQL Buddy.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply