Export (0) Print
Expand All

Checklist: Increasing Availability with Disaster Recovery

This topic describes the steps that you should follow to increase availability of a production BizTalk Server environment using disaster recovery. Disaster recovery is typically implemented after providing high availability with fault tolerance and/or load balancing.

Step Reference

Keep a written record of all changes to your BizTalk Server system.

Ensure that you have appropriate permissions to back up and restore BizTalk Server.

See Minimum Security User Rights (http://go.microsoft.com/fwlink/?LinkId=154374)

Create a highly available file share for purposes of storing the SQL Server logs. Configure a highly available file share at the hardware level using a SAN and/or at the Windows Server level by using Windows Clustering.

See How to create file shares on a cluster (http://support.microsoft.com/kb/224967)

Install and make available one or more standby SQL Server instances as the destination for BizTalk Server log shipping. The hardware for and the number of destination SQL Server instances should match the hardware for and number of SQL Server instances in the production environment. This will ensure that the destination SQL Server instance(s) can handle the same load as the production SQL Server instance(s).

See Installing SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=154377)

Prepare the disaster recovery site.

Prepare the Disaster Recovery Site

Back up and restore BizTalk Server databases

Configure BizTalk Server log shipping.

Configuring BizTalk Server Log Shipping

Configure the Backup BizTalk Server job.

How to Configure the Backup BizTalk Server Job (http://go.microsoft.com/fwlink/?LinkID=154072)

Configure the server where backups will be stored.

How to Configure the Destination System for Log Shipping (http://go.microsoft.com/fwlink/?LinkID=151402)

If you are using Business Activity Monitoring (BAM), back up the BAM databases.

Backing Up the BAM Analysis and Tracking Analysis Server Databases

If you are using BAM, back up the BAM portal application pools and virtual directories configuration information. If you are not using BAM, you do not need to perform this step.

How to Back Up the BAM Portal (http://go.microsoft.com/fwlink/?LinkId=154378)

Back up the BizTalk Server configuration file.

How to Back Up The BizTalk Server Configuration (http://go.microsoft.com/fwlink/?LinkId=154379)

If you are using Enterprise Single Sign-on, back up the master secret server.

How to Back Up the Master Secret (http://go.microsoft.com/fwlink/?LinkID=151395)

Steps Reference

Restore the BizTalk group.

Restoring the BizTalk Group

Recover the run-time computers running BizTalk Server.

Recovering the Runtime Computers

Recover BAM alerts.

How to Recover BAM Alerts (http://go.microsoft.com/fwlink/?LinkId=154380)

Recover the BAM portal.

How to Recover the BAM Portal (http://go.microsoft.com/fwlink/?LinkId=154381)

Restore the master secret server.

How to Restore the Master Secret (http://go.microsoft.com/fwlink/?LinkId=151394)

Restore the BizTalk Server databases.

How to Restore Your Databases (http://go.microsoft.com/fwlink/?LinkId=151406)

Update references to the BAM database names.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft