Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Problems with third-party backup tools

This page provides background information about the usage of external backup tools.

Which log files should be checked?
Configuration files for BACKINT
Problems with determining the EBID
Further information

Which log files should be checked?

In addition to files dbm.prt, dbm.knl, dbm.utl and knldiag you need to check file dbm.ebp in case of problems with third-party backup tools. In this file you can find e.g. the configuration parameters of the backup tool and where the problem occured (backup tool or database kernel). If this file is already overwritten (e.g. because command ext_backup_ids_get has been executed) you can find the information in file dbm.ebl - which is the history of files dbm.ebp.
Often problems with third-party backup tools are caused by wrong settings in the configuration files. Therefore you need to check these files as well.

back to top

Configuration files for BACKINT

Detailed information can be found in the documentation: Backint for SAP MaxDB
This section is meant to explain the interaction of the different components.
To create a backup using BACKINT FOR ORACLE an adapter program called BACKINT FOR MAXDB (obsolete name: BACKINT FOR SAP DB) is used. This adapter program is automatically installed when you install the SAP MaxDB software. To configure both programs correctly, you need to know how such a backup is done.
The database kernel writes the backup data into the configured pipe(s). BACKINT FOR MAXDB reads the data from the pipes and writes it into files. These files are copied by BACKINT FOR ORACLE to tapes.
The DBM server coordinates these actions:

  • it checks the configuration,
  • it creates the pipe(s),
  • it starts the backup in the database kernel,
  • it starts BACKINT FOR MAXDB (which starts BACKINT FOR ORACLE),
  • it checks the return codes of the different components and reports the success/failure to the administrator.

Therefore the DBM server needs to know

  • that BACKINT should be used fo the backup,
  • where BACKINT FOR MAXDB is located,
  • how BACKINT FOR MAXDB should be configured,
  • where BACKINT FOR ORACLE is located,
  • how BACKINT FOR ORACLE should be configured.

This is done using several parameter and configuration files.
Attention: although the configuration file and the parameter file for BACKINT FOR MAXDB look very similar, the parameter names need to be specified in a different way! In the parameter file a colon is required after the parameter names - in the configuration file the colon is not allowed!
Furthermore you have to make sure that the different input and output files have unique names.

In short, the following information is found in these files:

From the configuration file the Database Manager learns

  • where to find BACKINT FOR MAXDB,
  • where to find the parameter file par_file of BACKINT FOR MAXDB and
  • which files must be used as in_file and out_file for BACKINT FOR MAXDB.

From the file par_file the adapter program (BACKINT FOR MAXDB) learns

  • where to find BACKINT FOR ORACLE,
  • where to find the parameter file par_file2 of BACKINT FOR ORACLE,
  • which files must be used as in_file2 and out_file2 for BACKINT FOR ORACLE and
  • where to find its own history file.

From its configuration file par_file2 BACKINT FOR ORACLE learns

  • where to find the backup tool and how to use it. The format of this configuration file is described by the backup tool vendor. Some BACKINT FOR ORACLE implementations do not need such a configuration file (but use environment variables instead).

The following picture shows these configuration and parameter files:

back to top

Problems with determining the EBID

When an error occurs in the 'post backup steps' database manager returns an error but you find an error message in file knldiag or dbm.knl. The backup was finished successfully by the database kernel but the EBID could not be determined afterwards.
If the EBID cannot be determined it might not be possible to use this backup for a recovery. Therefore database manager reports such an error and logs it in files dbm.prt and dbm.ebp. You need to figure out why the EBID could not be determined.

Example for a problem with determining the EBID with Networker

Example for a wrong configuration of BACKINT

back to top

Further information

In the SAP MaxDB documentation (glossary entry Backup Tool) you can find the information about third-party backup tools. See also FAQ SAP MaxDB Third-party Backup Tools.
Detailed information about certification you find in SAP ICC . Use link SAP NetWeaver Application Server - Backup Tools for MaxDB.

Further information is also available in note 822240.

back to top

Relevant SAP MaxDB Documentation
Relevant SAP Notes

822240 FAQ  SAP MaxDB and third-party backup tools