Configuring for Disaster Recovery
The BizTalk Server Log Shipping feature extends the existing Backup BizTalk Server job. BizTalk Server Log Shipping eliminates the need to manually restore a series of backup sets produced by the backup job, and reduces downtime in the event of a system failure. BizTalk Server Log Shipping is a critical component for BizTalk disaster recovery procedures.
Note
Each application team must have a documented backup and restore plan for disaster recovery that complements the concepts provided in this topic. The overall plan should address the entire system, including applications and the components of the operating system.
Performing a disaster recovery operation is very similar to manually performing a restore of a BizTalk group to a new set of SQL Server database instances. The primary difference is that BizTalk Server log shipping applies logs continuously at the disaster recovery site, saving many manual steps. Therefore, only the last set of logs must be restored manually when BizTalk Server log shipping is implemented. Otherwise, the last full backup followed by all log backups since the last full backup would have to be manually restored. BizTalk Server log shipping reduces the effort for this manual process, speeding restoration of the disaster recovery site.
This section covers recommendations on production configuration to facilitate the disaster recovery process.
In This Section
See Also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for