You configure the SAP DB software with the aim of connecting the SAP DB database tools for saving, restoring, unloading, or loading data to an external backup tool.
You use the configuration file for Backint for SAP DB to inform the Database Manager where the Backint for SAP DB program is located, and how to communicate with it.
(See also: Functions of the SAP DB Adapter Program.)
If you want to use an external backup tool with a Backint for Oracle interface for a SAP DB database system, you first have to configure the connection between the SAP DB and the Backint for Oracle program (see Configuring the Backint for Oracle Connection). Creating the configuration file for the Backint for SAP DB is one of the required steps for this configuration.
If you want to use an external backup tool with a Backint for SAP DB interface for a SAP DB database system, you have to create a configuration file. For the most part, this corresponds to the configuration file in case 1. The differences are explained in the following description.
Here we can assume that the Backint for SAP DB interface of the vendor of the external backup tool corresponds to the Backint for SAP DB specification (see also the documentation Backup and Restore Interface for SAP DB Systems).
On every line in the configuration file you determine a parameter of the SAP DB adapter program. When you do this, at the beginning of each line you have to specify the keyword for the parameter and then the relevant value(s). Lines that do not begin with keywords are ignored by the system.
<key_string> <value_string>
<key_string> |
Keyword for a parameter; can consist of one or more words |
<value_string> |
Value(s) of the parameter |
You can define the following parameters for connecting Backint for SAP DB to the DBM server program:
Parameter |
Syntax |
Description |
Absolute path and name of the Backint program |
BACKINT <absolute_path>/<file_name> |
Case 1: Connecting
to a Backint for Oracle interface by using a SAP DB adapter program Case 2: Connecting
to the Backint for SAP DB interface of an external backup tool (third-party
vendor) |
Absolute path and name of the standard input file |
INPUT <absolute_path>/<file_name> |
The Database Manager creates these files temporarily and uses them for standard input, output, and error output for Backint for SAP DB. |
Absolute path and name of the standard output file |
OUTPUT <absolute_path>/<file_name> |
|
Absolute path and name of the standard error output file |
ERROROUTPUT <absolute_path>/<file_name> |
|
Absolute path and name of the configuration file of the Backint for SAP DB program |
PARAMETERFILE <absolute_path>/<file_name> |
Case 1: Connecting
to a Backint for Oracle interface by using a SAP DB adapter program Case 2: Connecting
to the Backint for SAP DB interface of an external backup tool (third-party
vendor) |
Time in seconds Time that the Database Manager waits for the end of the started Backint for SAP DB if action is successful |
TIMEOUT_SUCCESS <number> |
Default value: 300 Case 1: Connecting
to a Backint for Oracle interface by using a SAP DB adapter program Case 2: Connecting
to the Backint for SAP DB interface of an external backup tool
(third-party vendor) |
Time in seconds Time that the Database Manager waits for the end of the started Backint for SAP DB if errors occur |
TIMEOUT_FAILURE <number> |
Default value: 300 If an error occurs, the process terminates after this time, even if not all data was transferred. This ensures, for example, that during automatic night runs additional backup processes can start. |
Absolute path of the run directory of the source database |
ORIGINAL_RUNDIRECTORY <absolute_path> |
Default value: Run directory of the current database instance Specify this
parameter only for a migration. Pay attention to upper- and lowercase spelling when you specify this value. |
See also:
Example of a Configuration File for Backint for SAP DB