How to Configure the Backup BizTalk Server Job
1.
On the computer that
contains the BizTalk Management database, click Start, click Programs,
click Microsoft SQL Server 2005, and then click SQL Server Management
Studio.
2.
In the Connect to Server
dialog box, specify the name of the SQL Server where the BizTalk Server
databases reside and the appropriate authentication type, and then click Connect.
3.
In Microsoft SQL Server
Management Studio, double-click SQL Server Agent, and then click Jobs.
4.
In the details pane,
right-click Backup BizTalk Server (BizTalkMgmtDb), and then click Properties.
5.
In the Job Properties -
Backup BizTalk Server (BizTalkMgmtDb) dialog box, under Select a page,
click Steps.
6.
In the Job step list,
click BackupFull, and then click Edit.
7.
On the General page,
in the Command box, edit the command, and then click OK.
exec
[dbo].[sp_BackupAllFull_Schedule] 'd' /* Frequency */, 'BTS' /* Name */,
'<destination path>' /* location of backup files */, 0 (default) or 1 /*
ForceFullBackupAfterPartialSetFailure */
1.
Frequency: The default is d (daily). This is the recommended
setting. Other values include h (hourly), w (weekly), m
(monthly), or y (yearly).
2.
Name: The default is BTS. This is the recommended setting. The
name is used as part of the backup file name.
3. Location of backup files: Replace
'<destination path>' with the full path (the path must include the
single quotes) to the computer and folder where you want to back up the BizTalk
Server databases.
Caution
|
To
avoid potential data loss, you should specify a computer for your backup that
is different from the computer with the original data.
|
Caution
|
If you
specify a local path, then you have to manually copy all the files to the
same folder on the destination system whenever the Backup BizTalk Server job
creates new files. If you specify a remote path, it must be a UNC share such
as \\<ServerName>\<SharedDrive>\, where <ServerName>
is the name of the server where you want the files to be backed up using the
Backup BizTalk Server Job, and <SharedDrive> is name of the
shared folder.
|
4.
Force full backup after
partial backup failures: The default is 0
when not specified, which means that if a log backup fails, no full backups are
done until the next full backup frequency interval is reached. Replace with 1
if you want a full backup to be made whenever a log backup failure occurs.
8.
In the Job step list,
click MarkAndBackupLog, and then click Edit.
The
MarkAndBackupLog step is responsible for marking the logs and then backing them
up.
9.
On the General page,
in the Command box, replace '<destination path>'
with the full path (including single quotes) to the computer and folder where
you want to store the BizTalk Server database logs and then click OK.
The <destination path> may be local or a UNC path to another
server.
 Caution |
To
avoid potential data loss, the <destination path> should
specify a computer to store the database logs that is different from the
computer with the original database logs.
|
10. In the Job step list, click Clear Backup History,
and then click Edit.
11. On the General page, in the Command box, change DaysToKeep=<number>
to the number of days you want to keep the backup history, and then click OK
twice to close the Job Properties - Backup BizTalk Server (BizTalkMgmtDb)
dialog box.
 Note |
The DaysToKeep
parameter specifies how long the backup history is kept in the
Adm_BackupHistory table. Periodically clearing the backup history helps to
maintain the Adm_BackupHistory table at an appropriate size. The default
value for the DaysToKeep parameter is 14 days.
|
12. Change the backup schedule, if desired. For more information, see How to Schedule the Backup BizTalk Server Job.
| Note |
The
Backup BizTalk Server job runs the first time you configure it. By default,
on subsequent runs, the Backup BizTalk Server job performs a full backup once
a day and performs log backups every 15 minutes.
|
13. In the details pane, right-click the Backup BizTalk Server
job, and then click Enable.
In the Enable Jobs dialog box, the status changes to Success.
No comments:
Post a Comment
Post Your Comment...