Aspects of Backup for BizTalk Databases

Table of Contents

Introduction

When it comes to making backups of BizTalk, there is only one way that is supported by Microsoft; you need to make Log Shipping Backups. A number of usable articles have been written about making backups of BizTalk databases and other related databases. These
articles are summed up and categorized in this article.

How to add/remove custom databases to the backup

In extension of making backups of your BizTalk databases,
this article explains how custom databases should be added to the Backup BizTalk Server job.
The article also gives some more inside information about the view which shows the databases which are in your BizTalk backup

How to remove custom database from BizTalk Log Shipping can be found
here

Note: Only the addition of SQL Server databases is supported.

Clean up backup artifacts

Automatically remove old backup files with a SQL Server Maintenance Plan is described
here

Automatically remove old backup files with a SQL Script is described
here

When things go wrong

Backup BizTalk Server job failed: The last step to run was step 2 (BackupFull). The job was requested to start at step 1 (Set Compression Option) is
here

Backup BizTalk Server job failed: The job failed. The Job was invoked by Schedule 9 (MarkAndBackupLogSched). The last step to run was step 2 (BackupFull) is
here

Backup BizTalk Server job failed: The job failed. The Job was invoked by User domain\user. The last step to run was step 3 (MarkAndBackupLog). The job was requested to start at step 1 (Set Compression Option) is
here

The "Backup BizTalk Server" job fails when backup files accumulate over time in the Microsoft BizTalk Server database server is
here

BUG: The "Backup BizTalk Server" SQL job fails with an error because the adm_OtherBackupDatabases table is not created is
here

Backup BizTalk Job not able to backup databases which reside on the different SQL server is
here