The following applies to BAM in BizTalk 2006. It would work similarly in BizTalk 2004, without SQL NS databases.
Deployment and Removal
To ensure consistent schema across all BAM databases, run the “Backup BizTalk Server” SQL job for each deployment of activities and/or views. In addition, backup the DTS packages, BAM analysis, star schema and archive databases.
Runtime
To ensure databases are in sync after a restore, it is necessary to back up the BAM databases in the following order:
- Run SQL agent job “Backup BizTalk Server” to back up BAM Primary Import, SQL NS as well as other BizTalk databases.
- Run BAM analysis and data maintenance DTS/SSIS packages for all activities and cubes respectively.
- Backup BAM star schema, analysis and archive databases.
The BAM star schema, analysis and archive databases are modified when the analysis and data maintenance DTS/SSIS packages are executed. Hence, in case of failure of Primary Import, restore the backup of star schema, analysis and archive databases BEFORE the last successful backup of Primary Import.
It is possible that the archive database may fail in between the successful execution of the data maintenance DTS/SSIS package and the next backup of the database. In order to ensure that at any time a complete set of archived data can be recovered, modify the data maintenance DTS/SSIS package for each activity to insert a step to backup the Archive database before the last step “End Archiving”. The “End Archiving” step deletes the archived data from Primary Import database, updates metadata tables and views.
