Procedure documentationCreating the Configuration File for Backint for SAP MaxDB Locate this document in the navigation structure

 

Creating the configuration file for Backint for SAP MaxDB is a necessary step for connecting SAP MaxDB to a third-party backup tool via the Backint for Oracle interface or the Backint for SAP MaxDB interface. By means of this configuration file, you inform Database Manager where the Backint for SAP MaxDB program is located and how to address it.

Case 1: Connecting to Backint for Oracle Using the SAP MaxDB Adapter Program

If you want to use a third-party backup tool with a Backint for Oracle interface for an SAP MaxDB database system, you first must configure the connection between SAP MaxDB and the Backint for Oracle program (see Configuring the Backint for Oracle Connection). Creating the configuration file for Backint for SAP MaxDB is one of the necessary steps for this configuration.

Case 2: Connecting to the Backint for SAP MaxDB Interface of a Backup Tool

If you want to use a third-party backup tool with a Backint for SAP MaxDB interface for an SAP MaxDB database system, you must create a configuration file for Backint for SAP MaxDB. Essentially, this is the same as the configuration file in case 1. Differences are taken into account in the following description.

It is assumed that the Backint for SAP MaxDB interface of the third-party vendor meets the Backint for SAP MaxDB specification.

Procedure

Specify a parameter of Database Manager in each line in the configuration file. Specify the keyword for the parameter at the beginning of each line and then the relevant value(s).

Lines that do not begin with keywords are ignored by the system.

Syntax

<key_string> <value_string>

Options

Option

Description

<key_string>

Keyword for a parameter,

can consist of one or more words

<value_string>

Value(s) of the parameter

Define the following parameters for connecting Backint for SAP MaxDB to Database Manager:

Parameters

Syntax

Description

Absolute path and name of the Backint program

BACKINT <absolute_path>/<file_name>

Case 1- Connecting to a Backint for Oracle interface using the SAP MaxDB adapter program:

Enter the absolute path and name of the adapter program supplied with SAP MaxDB.

Case 2 - Connecting to the Backint for MaxDB interface of the third-party backup tool:

Enter the absolute path and name of the Backint for SAP MaxDB program.

Absolute path and name of the standard input file

INPUT <absolute_path>/<file_name>

Database Manager creates these files temporarily and uses them as standard input for Backint for SAP MaxDB.

The default file is bsi.in in the run directory of the database.

Absolute path and name of the standard output file

OUTPUT <absolute_path>/<file_name>

Database Manager creates these files temporarily and uses them as standard output for Backint for SAP MaxDB.

The default file is bsi.out in the run directory of the database.

Absolute path and name of the standard error output file

ERROROUTPUT <absolute_path>/<file_name>

Database Manager creates these files temporarily and uses them as standard error output for Backint for SAP MaxDB.

The default file is bsi.err in the run directory of the database.

Absolute path and name of the configuration file of the Backint for SAP MaxDB program

PARAMETERFILE <absolute_path>/<file_name>

Case 1- Connecting to a Backint for Oracle interface using the SAP MaxDB adapter program:

Enter the absolute path and name of the parameter file for the adapter program.

Case 2 - Connecting to the Backint for SAP MaxDB interface of a third-party backup tool:

Enter the absolute path and name of a configuration file (you may have to define this file) for the Backint for SAP MaxDB program.

Time in seconds.

Time after which the backup tool automatically quits once the database kernel has copied all data successfully

TIMEOUT_SUCCESS <number>

Default value: 300

Case 1- Connecting to a Backint for Oracle interface using the SAP MaxDB adapter program:

Choose a value sufficiently large to enable the third-party backup tool to back up all data copied onto tape during this time. The number of temporary files and their configured size are defining factors for this.

Case 2 - Connecting to the Backint for SAP MaxDB interface of a third-party backup tool:

Time span after which Database Manager should quit the backup tool if all data has been copied to the pipes.

Note that the backup tool always quits after the defined period, regardless of whether all data copied from the database kernel has been backed up or not.

Time in seconds.

Time after which the third-party backup tool automatically quits if the database kernel has interrupted the backup due to an error.

TIMEOUT_FAILURE <number>

Default value: 300

Make sure you allow sufficient time for the third-party backup tool to save all data copied by the database kernel, as the backup tool always quits when the timeout is reached, even if not all the copied data has been saved. On the other hand, you must be careful not to specify too much time. Otherwise a situation may occur where a backup interrupted by the database kernel blocks other backups from being started (such as automatic nighttime backups).

Absolute path of the run directory of the source database

ORIGINAL_RUNDIRECTORY <absolute_path>

Default value: Run directory of the current database

Only specify this parameter for a migration. A prerequisite for migration from one computer to another is that the version of Backint for SAP MaxDB that you are using can make backups from the source computer available on the target computer.

Pay attention to uppercase and lowercase spelling when you specify this value.

Activating and deactivating the check mechanism of Backint for SAP MaxDB implementation.

This checks whether backups listed in the backup history are actually available in the backup tool.

CHECK_AVAILABILITY <option>

<option> :: = YES | NO | <definition>

<definition> :: = <number> BACKUPS | <number> <time_period>

<time_period> :: = days | weeks | months | years

YES: The system checks whether backups listed in the backup history are available for the system in the backup tool (default value)

NO: The system assumes that backups listed in the backup history are actually available in the third-party backup tool without carrying out a check beforehand.

<definition>: The system checks whether the specified number of last backups or the backups made in the designated period are available. It assumes that the rest of the backups are available.

<number>: Number, 1 ≤ <number> ≤ 2^31–1 applies

days: Days

weeks: Weeks

months: Months

years: Years

Note Note

Define this parameter only if you think the system is taking too long to evaluate external backup IDs.

End of the note.

More Information

Example of a Configuration File for Backint for SAP MaxDB

How the SAP MaxDB Adapter Program Works

Concepts of the Database System, Database Tools

For the Backint for SAP MaxDB documentation, see the SAP MaxDB archive at http://maxdb.sap.com/archive/.