Business Continuity and Disaster Recovery in BizTalk Services
Updated: November 27, 2015
Describes business continuity and disaster recovery in Microsoft Azure BizTalk Services. It includes the possible issues and the capabilities provided.
For Microsoft Azure BizTalk Services, Business Continuity issues belong to one of the following categories:
Failure of individual servers, devices or network connectivity
Corruption, unwanted modification or deletion of data
Widespread loss of data center facilities
For these types of failures, Azure Business Continuity Technical Guidance provides some good information, including:
Describes the Fabric Controller (FC); which monitors and manages role instances.
Tips for developers when creating applications; including storing persistent data in an Azure Store Account or SQL Database.
Tips for administrators, including using the Scale feature to handle increase or decrease demands.
To provide high availability, every Azure BizTalk Service (except the Developer Edition) includes at least two role instances. Some Editions can also be scaled to add additional Units. See BizTalk Services: Developer, Basic, Standard and Premium Editions Chart for more details.
An Microsoft Azure BizTalk Service uses Microsoft Azure SQL Database. The SQL Database has built-in features that provide fault tolerance, as described in Business Continuity in Azure SQL Database.
Data corruption, modifications, and deletions can occur for many reasons; including application errors, operator errors, and so on. Microsoft Azure BizTalk Services provides Backup and Restore functionality. It is recommended to create a backup of the BizTalk Service on a regular basis, including whenever a management operation (like updating the SSL certificate or modifying an EDI agreement) is made to the BizTalk Service. BizTalk Services: Backup and Restore lists the backup and restore options for a BizTalk Service.
The Backup-Restore option doesn’t back up the BizTalk Services dependencies, including Microsoft Azure SQL Databases, Microsoft Azure Storage, and Microsoft Azure Access Control. For these dependencies, consider the following:
Business Continuity in Azure SQL Database provides information on Microsoft Azure SQL Database.
Azure Business Continuity Technical Guidance provides information on Microsoft Azure Storage. It is recommended to enable geo-replication on the Storage account.
For Microsoft Azure Access Control, you can create a new namespace. Azure Business Continuity Technical Guidance provides information on Microsoft Azure Access Control.
When you provision or create a backup of the BizTalk Service, you specify the datacenter. It is recommended to create backups to a different datacenter. If a datacenter disaster occurs, use the Restore functionality to restore an existing backup. BizTalk Services: Backup and Restore lists the backup and restore options for a BizTalk Service.
The Azure Service Dashboard shows the status of the backend components of the BizTalk Service. Any issues with the backend components are communicated in this dashboard. This dashboard also lists the health state of any dependent components.
Backup the BizTalk Service often; daily is ideal.