How the SAP Agent works

The SAP Agent acts as a client for Backup Exec. Through the biparam.ini file, you set Backup Exec parameters for the jobs that you submit from SAP interfaces. For example, you can set a job name, specify a server or device to use for the job, or specify the backup compression mode.

The SAP Agent connects to your Backup Exec server. The requests are processed through Backup Exec. Jobs that you submit from SAP interfaces, through the SAP Agent, are treated as Run Now jobs. If all drives are busy, jobs can be queued in a Backup Exec job queue. From the queue, the Backup Exec administrator can edit or cancel the job.

When jobs are complete, Backup Exec writes a standard job log as it does for any submitted job. You can view the job log from the Backup Exec administration console. The SAP Agent sends the results of its jobs to the SAP tools. When a job is initiated by a SAP interface, a job log is produced with an eight-character name that represents the job. The SAP system stores the job log in the following directory:


where <x> is the database installation drive and <SID> is the system ID of the Oracle instance. The file is a plain ASCII text file that you can view with any text editor.

The SAP Agent displays errors and their details on the console, so some problems can be solved without looking at the log file.

You can type either of the following commands to view command line help:

The _backint.xml file, which stores Backup Exec catalog information about the job, is placed in the folder local to BRTOOLS, a SAP utility program. Generally the path is as follows:


In the event of a disaster, you must restore this file to restore data to the SAP server.

More Information

About system level SAP backup jobs

About performing disaster recovery using the SAP Agent