Schedule the Backup BizTalk Server Job
The Backup BizTalk Server job runs as scheduled by the SQL Server Agent service. If you want to create more frequent or less frequent backups, you can change the schedule of the Backup BizTalk Server job by using SQL Server Management Studio.
Sign in with an account that is a member of the SQL Server sysadmin fixed server role.
Schedule the Backup BizTalk Server job
On the SQL Server that hosts the BizTalk Management database, open SQL Server Management Studio.
In Connect to Server, enter the name of the SQL Server where the BizTalk Server databases reside, select the authentication type, and then Connect.
In the Object Explorer, double-click SQL Server Agent, and then select Jobs.
In the details pane, right-click Backup BizTalk Server (BizTalkMgmtDb), and then select Properties.
In the Job Properties - Backup BizTalk Server (BizTalkMgmtDb), under Select a page, select Steps.
In the Job step list, select BackupFull, and then select Edit.
In the Job Step Properties - BackupFull, in the Command box, update the command by changing the frequency to run a full backup: 'h' (hourly), 'd' (daily), 'w' (weekly), 'm' (monthly), 'y' (yearly). Select OK.
The first time the Backup BizTalk Server job runs, it completes a full backup.
Configure additional @frequency parameters:
@ForceFullBackupAfterPartialSetFailure: The default value is false. When false, if the full backup fails, the system waits for the next cycle until the full backup is made.
If your @frequency setting is long (like weekly, monthly, yearly), then setting this parameter to false could be dangerous. In this scenario, it may be best to set this flag to true. When true, every time there is a failure, the system forces itself to create a full backup. There may be a small performance impact, but it’s safter to have a recoverable system.
@BackupHour: The default valueis NULL. This parameter is directly related to @Frequency. When you set the frequency to h (hourly), you set which hour of the day you want the full backup to run. You can choose a value between 0 (midnight) to 23 (11 PM). If left blank, the full backup runs every hour.
If you set this parameter with a number outside the 0 to 23 range (for example, 100 or -1), the system forces it to 0.
@UseLocalTime: An extra parameter that states to use local time. By default, the job works with UTC time. So if you live in Australia (which is UTC + 10 hours), your backup runs at 10am rather than midnight. As a best practice, it is recommended to set this to 1 (true).
In the Job Properties - Backup BizTalk Server (BizTalkMgmtDb), under Select a page, click Schedules.
In the Schedule list, click MarkAndBackupLogSched, and then click Edit.
In the Job Schedule Properties - MarkAndBackupLogSched, in Schedule type, select Recurring from the drop-down list.
By default, the job is scheduled to run every 15 minutes.
You can change this value according to your requirements, but first test in non-production environment. Setting this value too low results in frequent backups, and adds to the background load in your SQL environment. Setting this value too high may increase the size of transaction logs, and impact performance. In some situations, it is recommended to leave the default value.
Update the schedule if desired, and then select OK.
Scheduling Jobs provides more details.
In the Job Properties - Backup BizTalk Server (BizTalkMgmtDb), click OK.