Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for SAP Administrator's Guide
  3. Configuring NetBackup for SAP
  4. About SAP configuration files
  5. Modifying the bsi.env file (NetBackup for SAP on MaxDB databases)
Veritas NetBackup™ for SAP Administrator's Guide

Modifying the bsi.env file (NetBackup for SAP on MaxDB databases)

The bsi.env file specifies the following:

  • The backint for MaxDB program's location, which is NetBackup for SAP on MaxDB.

  • How to communicate with backint.

The database manager uses this information when it performs backups and restores.

bsi.env is the default name for this configuration file. If you want to change this name, you can specify a different name in the BSI_ENV environment variable in the MaxDB user environment.

Table: bsi.env file parameters lists the parameters that you can include in the bsi.env file.

Table: bsi.env file parameters

Parameter

Description

BACKINT /usr/openv/netbackup/bin/backint 
BACKINT <install_path>\Veritas\NetBackup
\bin\backint.exe 

Specifies the absolute path and file name of the backint for MaxDB program.

INPUT absolute_path/file_name
INPUT absolute_path\file_name
OUTPUT absolute_path/file_name
OUTPUT absolute_path\file_name
ERROROUTPUT absolute_path/file_name
ERROROUTPUT absolute_path\file_name

The INPUT parameter specifies the absolute path and file name of the standard input file. The OUTPUT parameter specifies the absolute path and file name of the standard output file. The ERROROUTPUT file specifies the absolute path and file name of the standard error output file.

The database manager creates these files temporarily and uses them for standard input, output, and error output for backint for MaxDB.

PARAMETERFILE absolute_path/file_name
PARAMETERFILE absolute_path\file_name

Specifies the absolute path and file name of the configuration file for the backint for MaxDB program, initSAP.utl.

TIMEOUT_SUCCESS seconds

The number of seconds after which the backup tool exits and after the database kernel has copied all data successfully. Default is 300.

This value is the 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. This exit occurs whether all the data is copied from the database kernel is backed up by the backup tool or not.

TIMEOUT_FAILURE seconds

This parameter is effective only if the database kernel has stopped the backup due to an error. In such a case, seconds specifies the number of seconds after which the backup tool exits. Default is 300.

Allow enough time for the backup tool to save all the data that the database kernel copies. The backup tool always exits when this timeout is reached, even if not all of the copied data has been saved yet. However, do not specify too much time. You risk a situation in which a backup that is stopped by the database kernel blocks other backups, such as automatic nightly backups, from being started.

ORIGINAL_RUNDIRECTORY absolute_path

Specifies the absolute path of the run directory of the source database. The default value is the run directory of the current database instance. This value is case-sensitive.

Specify this parameter only for a migration. The following prerequisite must be met for migration from one computer to another:

The version of backint for MaxDB that you use is capable of backing up from the source computer available on the target computer.

To create a MaxDB configuration file

  1. Use a text editor to create the MaxDB configuration file, bsi.env.

    You can give the MaxDB configuration file a name other than bsi.env. If so, edit the BSI_ENV environment variable and include the full path to this file.

  2. Use the parameters to specify backup characteristics.

    You must include the following parameters in bsi.env: BACKINT, INPUT, OUTPUT, ERROROUTPUT, and PARAMETERFILE. All other parameters are optional.

    The following is an example of a file with the minimum configuration specified:

    UNIX or Linux:

    BACKINT /usr/openv/netbackup/bin/backint
    INPUT /export/home/sapdb/logs/backint.in
    OUTPUT /export/home/sapdb/logs/backint.out
    ERROROUTPUT /export/home/sapdb/logs/backint.err
    PARAMETERFILE /export/home/sapdb/indep_data/wrk/initSAP.utl

    Windows:

    BACKINT install_path\NetBackup\bin\backint
    INPUT C:\sapdb\logs\backint.in
    OUTPUT C:\sapdb\logs\backint.out
    ERROROUTPUT C:\sapdb\logs\backint.err
    PARAMETERFILE C:\sapdb\indep_data\wrk\initSAP.utl

Feedback

Was this page helpful?
Previous

Example initSID.sap file (NetBackup for SAP on Oracle databases only)

Next

Backing up files mounted with LOFS with NetBackup for SAP (UNIX or Linux)

Feedback

Was this page helpful?