Microsoft IT: A case study on Business Continuity and Disaster Recovery – SQL Server 2012
SQL Server Technical Article
Writer: Srinivas Venbakam Vengadam, Microsoft | Srikiran Tadikonda, Microsoft | Kishore B V Bondada, Microsoft
Reviewed By: Manoj Badgujar, Microsoft | Mandi Ohlinger, Microsoft
Contributors: Supriya Naik, Microsoft | Manoj Badgujar, Microsoft | Kishore B V Bondada, Microsoft | Vijay Shankar, Microsoft
Published: August 2013
Applies to: SQL Server 2012, BCDR
Summary: This paper shares the approach used by Microsoft IT to do the following:
- Upgrade a database server from SQL Server 2008 R2 to SQL Server 2012.
- Set up BCDR for all the dependent applications and services with minimal downtime.
When the database sizes are huge, are transactional, and have replications from/to another SQL Server (that does not support available groups), you can use some of the alternatives discussed in this white paper to manage your downtimes and avoid replication re-initializations. This white paper walks through disaster scenarios related to a database server; it does not cover disaster scenarios of web or application servers.
This content is suitable for developers or architects and database administrators. It is assumed that readers of this white paper have basic knowledge of SQL Server 2012 AlwaysOn, SQL transactional replications, and SQL Server administration.
To review the document, please download the Microsoft IT: A case study on Business Continuity and Disaster Recovery - SQL Server 2012 Word document.