Export (0) Print
Expand All

Backing Up and Restoring BizTalk Server Databases

You use the Backup BizTalk Server job to back up all of the databases in your BizTalk Server source system, except for some databases used by Business Activity Services (BAS) and Business Activity Monitoring (BAM). The source system is the server or group of servers that contain live data. Because the BAS and BAM databases have different backup and restore requirements, these databases are backed up and restored using other methods.

A common way to back up databases is to create a complete backup of the database once per day (if the database is not too large), then periodically make a copy of the transaction logs. This method is not suitable for use with BizTalk Server, because BizTalk may have distributed transactions pending among several databases. This is why BizTalk Server relies on transaction log marking, and the backup procedures that follow. For more information about transaction log marking, see Marked Transactions, Full Backups, and Log Backups.

Backing up the BizTalk Server databases and restoring them involves the following steps:

  1. Configuring the Backup BizTalk Server job

    Before you can back up the BizTalk Server databases, you must first configure the Backup BizTalk Server job on the source system, which directs backups to be automatically written to a folder where they can then be used to restore the databases on the destination system. The destination system is the server or group of servers that will be used to restore the database backups produced by the source system. For more information about this step, see How to Configure the Backup BizTalk Server Job.

    Remember to make a backup copy of the Backup BizTalk Server job after you have configured it. The easiest way to do this is to script the backup job to a file. For more information about backing up jobs, see How to Back Up and Restore SQL Agent Jobs.

  2. Configuring the destination system for log shipping

    You must also configure the destination system for log shipping, which provides standby server capabilities and reduces downtime in the event of a system failure. For more information about this step, see How to Configure the Destination System for Log Shipping.

  3. Restoring the databases

    When a hardware failure occurs, you can restore your databases using the backups and logs sent to your destination system. For more information about this step, see How to Restore Your Databases.

The following tables describe the databases used by BizTalk Server and identify which methods are used to back up the databases.

Databases Backed Up by the Backup BizTalk Server Job

The following table lists the databases that are backed up and restored as a part of the Backup BizTalk Server job. You can modify the Backup BizTalk Server job to back up custom databases by adding them to the adm_OtherBackupDatabases table. For more information, see How to Back Up Custom Databases.

Database Default database name Description

BAM Primary Import database

BAMPrimaryImport

This is the database where the Business Activity Monitoring (BAM) collects raw tracking data.

BAM Notification Services Application database

BAMAlertsApplication

This database contains alert information for BAM notifications. For example, when you create an alert using the BAM portal, entries are inserted in the database specifying the conditions and events to which the alert pertains, as well as other supporting data items for the alert.

BAM Notification Services Instance database

BAMAlertsNSMain

This database contains instance information specifying how the notification services connect to the system that BAM is monitoring.

HWS Administration database

BizTalkHwsDb

This database contains all administration information related to Human Workflow Services (HWS).

BizTalk Tracking database

BizTalkDTADb

This database stores health monitoring data tracked by the BizTalk Server tracking engine.

BizTalk Management database

BizTalkMgmtDb

This database is the central meta-information store for all instances of BizTalk Server.

BizTalk MessageBox database

BizTalkMsgBoxDb

This database is used by the BizTalk Server engine for routing, queuing, instance management, and a variety of other tasks.

Rule Engine database

BizTalkRuleEngineDb

This database is a repository for:

  • Policies, which are sets of related rules.

  • Vocabularies, which are collections of user-friendly, domain-specific names for data references in rules.

SSO database

SSODB

This Enterprise Single Sign-On database securely stores the configuration information for receive locations.

TPM database

TPM

This database stores trading partner data for Business Activity Services (BAS). By default, TPM database is combined with BizTalk Management (BizTalkMgmtDb) database.

BizTalk Base EDI database

BizTalkEDIdb

This database stores state for the Base electronic data interchange (EDI) adapter, which has been deprecated in BizTalk Server 2006 R2. The Base EDI adapter can be used in upgrade scenarios, but for new installations of BizTalk Server 2006 R2, use the native EDI and AS2 functionality. For more information, see BizTalk Server 2006 R2 EDI and AS2 Processing.

Databases Backed Up by the BAS Backup Process

The following table lists the Microsoft Windows SharePoint Services databases that are backed up and restored using the procedures in Backing Up and Restoring BAS:

Database Default database name Description

Windows SharePoint Services configuration database

User-defined

This database contains all of the global settings for the server.

Windows SharePoint Services content database

User-defined

This database contains all of the site content, such as list items and documents.

Databases Backed Up by the BAM Backup Process

The following table lists the databases that are backed up and restored using the procedures in Backing Up and Restoring BAM:

Database Default database name Description

BAM Star Schema

BAMStarSchema

This database contains the staging table, and the measure and dimension tables.

BAM Analysis

BAMAnalysis

This database contains BAM OLAP cubes for both online and offline analysis.

BAM Archive

BAMArchive

This database archives old business activity data. Create a BAM Archive database to minimize the accumulation of business activity data in the BAM Primary Import database.

Tracking Analysis Server

BizTalkAnalysisDb

This database stores health monitoring online analytical processing (OLAP) cubes.

Community Additions

Show:
© 2014 Microsoft