Updated Azure business continuity technical guidance

Adam Glick

We are pleased to announce the update to the resiliency technical guidance documentation for Microsoft Azure. This document was previously called the business continuity technical guidance whitepaper that was posted on MSDN. This document has been updated to provide a better understanding of options with our current service offerings as well as how to think about using Azure to recover from various kinds of failures. The published article series covers different failure types that span from local to regional, different business continuity scenarios, and how to design a disaster recovery plan that can help you use Azure features and resources to meet your own disaster recovery and business continuity needs. In particular, this guidance deals with the following scenarios:

Recovery from local failures – This pattern shows how to design for high availability against failures that are localized to particular systems or hardware. Recovery from an Azure region-wide service disruption – This pattern shows how to think about recovery from a disaster that creates a service disruption across an entire Azure region. Recovery from on-premises to Azure – This pattern helps for considering Azure as a disaster recovery site for on-premises/co-location hosted applications. Recovery from data corruption or accidental deletion – This is a pattern that is most associated with backup and archiving. This describes how to handle challenges like dropped tables/databases, data corruption, or errors that went undetected for a period of time.

We hope this guidance is useful in creating better plans for business continuity, disaster recovery, and resiliency. As always, Microsoft Azure wants to enable our customer’s success and your feedback on these articles is always appreciated and encouraged. Please feel free to leave comments in the comments section below or email us at ResiliencyFeedback@microsoft.com.


Discussion is closed.

Feedback usabilla icon