Friday, 23 March 2012 18:53

Forcing a Full BizTalk Backup

Written by 
Rate this item
(7 votes)

BizTalk uses multiple databases. Think about the Configuration database (BizTalkMgmtDb), the MessageBox database (BizTalkMsgboxDb), the Tracking database (BizTalkDTADb) etc. etc. Beside these databases, your system might also have its own ‘custom’ database(s). Together these databases define the state of your application or system.

All these databases should be backed up by the Backup BizTalk Server job on SQL Server. This job makes both Full and Log backups. Normally a Full backup is made every 24 hours and a Log backup every 15 minutes.

In this article I’ll describe how you can force the Backup job to make a Full backup, which might be handy when you are preparing an upgrade of your application or system. Further I’ll describe how you can monitor the progress of the Backup job and how you can see where the backups are written to.

Using sp_ForceFullBackup

The proper way to force a Full backup from BizTalk is by executing the Stored Procedure ‘sp_ForceFullBackup’ which resides in the Configuration database.

Perform the following steps:

  • Start SQL Server Management Studio (or SSMS)
  • Connect to the Database Server which contains the BizTalk Configuration database (BizTalkMgmtDb)
  • Right click on the name of the database and select ‘New Query’
  • Type ‘exec sp_ForceFullBackup’ and hit F5

1 - sp ForceFullBackup

Now you have forced a full backup. But it won’t run immediately. Don’t worry though. The next time the backup job is started, normally within 15 minutes, it will notice that a full backup has been forced, and a full backup will be made.

What this Stored Procedure actually does is changing a value in the table adm_BackupSettings. In BizTalk 2010 this table contains only one row and two fields. One field, of type bit, named ForceFull normally has the value ‘False’, but the Stored Procedure changes it to ‘True’.

Starting the backup

If you want to start the backup immediately, perform the following steps:

  • In SSMS expand the SQL Server Agent node, which can be found in the Object Explorer
  • Expand the Jobs Node and in the right pane all SQL Server Agent jobs appear
  • Right click on the Backup BizTalk Server job and click on ‘Start Job at Step..’
  • In the dialog that appears, click the Start button

2 - StartFullBackUp

Monitoring the backup

The progress of the backup job can be monitored at the following locations:

  • The view in the right pane where all SQL Server Agent jobs are shown contains a column ‘Status’. When the backup job is active, the status is ‘Executing’
  • The Job Activity Monitor: when the job is active, this monitor shows that job

3 - SQLServerAgentJobs

4 - ActivityMonitor

View the results of the backup

Right click on the ‘Backup BizTalk Server’ job and choose ‘View History’ to find out if the job has done its work properly. If not, you’ll see want went wrong there as well.

The Backup BizTalk Server job has separate steps for making a Full or a Log backup. Each step performs another Stored Procedure and both Stored Procedures have a parameter to set the location of the backup.
By opening the job and viewing the command line of the steps ‘BackupFull’ and ‘MarkAndbackupLog’ you can find out where the backups are created.

5 - BackupHistory

6 - Backups

Read 3427 times Last modified on Friday, 23 March 2012 19:47
Lex Hegt

Lex Hegt currently works as a BizTalk architect/administrator at Ordina. Although he works in the Information Technology for more than 25 years, he 'only' works with BizTalk for 8 years. His first BizTalk assignments were as a developer, but since a couple of years he works as an administrator.
Besides this blog he also blogs for many years at the BIA blog and does he maintain some tools, namely BizTalk Processing Monitor and BTSDecompress. He has certifications for BizTalk Server 2006, BizTalk Server 2006 R2 and BizTalk Server 2010.

twitterlinkedin

Website: biztalkia.blogspot.com

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.