Creating the Configuration File for Backint for MaxDB

Use

You configure the MaxDB software with the aim of connecting the MaxDB database tools for backing up, restoring, exporting, or importing data to a backup tool from another provider.

You use the configuration file for Backint for MaxDB to inform the Database Manager where the Backint for MaxDB program is located and how to communicate with it.

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

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

(See also: How the MaxDB Adapter Program Works.)

Case 2: Connecting to the Backint for MaxDB Interface of a Backup Tool from Another Provider

If you want to use a backup tool with a Backint for MaxDB interface for a MaxDB 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.

It is assumed that the Backint for MaxDB interface of the third-party vendor meets the Backint for MaxDB specification (see also the documentation Backint for MaxDB).

Procedure

You specify a parameter of the Database Manager in every line in the configuration file. 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.

Syntax

<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 MaxDB to the Database Manager:

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 MaxDB adapter program
Specify the absolute path and name of the adapter program that was delivered with MaxDB.

Case 2: Connecting to the Backint for MaxDB interface of a backup tool (third-party vendor)
Specify the absolute path and name of the Backint for MaxDB program.

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 for Backint for MaxDB.

The default file is bsi.in in the working directory of the database instance.

Absolute path and name of standard output file

OUTPUT <absolute_path>/<file_name>

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

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

Absolute path and name the standard error output file

ERROROUTPUT <absolute_path>/<file_name>

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

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

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

PARAMETERFILE <absolute_path>/<file_name>

Case 1: Connecting to a Backint for Oracle interface by using a MaxDB adapter program
Specify the absolute path and name of the parameter file of the adapter program.

Case 2: Connecting to the Backint for MaxDB interface of the backup tool: Specify the absolute path and name of a configuration file for the Backint for MaxDB program, if it was necessary to create one.

Time in seconds,

Time after which the backup tool exits, after the database kernel has copied all data successfully

TIMEOUT_SUCCESS <number>

Default value: 300

Case 1 - Connecting to a Backint for Oracle interface by using a MaxDB adapter program: Make sure that you allow enough time so that the backup tool can save all copied data to a tape. The number of temporary files and their configured sizes are the most important factors here.

Case 2 - Connecting to the Backint for MaxDB interface of the backup tool: Period of time after which the Database Manager terminates the backup tool, if all data has been copied to the pipes.

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

Time in seconds,

Time after which the backup tool exits, if the database kernel has stopped the backup due to an error.

TIMEOUT_FAILURE <number>

Default value: 300

Make sure that you allow enough time so that the backup tool can save all data copied by the database kernel. This is because the backup tool always exits when this timeout is reached, even if not all of the copied data has been saved yet. On the other hand, do not specify too much time. Otherwise, you risk a situation where a backup stopped by the database kernel blocks other backups (such as automatic backups at night) from being started.

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.
The prerequisite for the migration from one computer to another is that the version of Backint for MaxDB that you are using can make backups from the source computer available on the target computer.

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

See also:

Example for a Configuration File for Backint for MaxDB