Documentation PDF

Protect. Access. Comply. Share.

Configuring the SAP MaxDB Parameter
File
 Updated Monday, November 13, 2023

After you install the SAP MaxDB agent, configure the parameter file.

Procedure
1. Run the command from the DBM client interface to associate the SAP MaxDB database with the
product software.

Windows Configuration

 Note

You must use double quotes when there is a space in the path that points to the backint.conf
file.

dbm_configset -raw BSI_ENV <software install path>\SapMaxDbAgent\backint.conf

Example

In this example, you do not need the double quotes.

dbm_configset -raw BSI_ENV C:\SapMaxDB\backint.conf

In this example, you must use double quotes because the path contains a space ("Program Files").

dbm_configset -raw BSI_ENV "C:\Program

Files\CommVault\ContentStore\SapMaxDbAgent\backint.conf"

UNIX Configuration

Log on to the database and then type the following command from the DBM client interface,
substituting the database_name, user_name, and password:
 dbm_configset -raw BSI_ENV <software install path>/SapMaxDbAgent/backint.conf
dbm_configset -raw set_variable_0 LD_LIBRARY_PATH=/<software install
path>/Base dbm_configset -raw set_variable_1 SHLIB_PATH=/<software install
path>/Base

Example

dbm_configset -raw BSI_ENV /opt/commvault/SapMaxDbAgent/backint.conf

dbm_configset -raw set_variable_0 LD_LIBRARY_PATH=/opt/commvault/Base
dbm_configset -raw set_variable_1 SHLIB_PATH=/opt/commvault/Base

Configure the shared library path in the .profile file from the root directory.

AIX and HP-UX Configuration:

SHLIB_PATH=/<software install path>/Base:/<software install path>/Base64

export SHLIB_PATH For Linux and Solaris: LD_LIBRARY_PATH=/<software install
path>/Base:/<software install path>/Base64 export LD_LIBRARY_PATH

2. Configure the SAP MaxDB parameter file (param). Include the required and optional parameters.

For information on the parameters, see Supported SAP MaxDB Configuration File Parameters.

Windows Configuration

The parameter file is located under the <software_install_folder>\SapMaxDbAgent.

numstreams 1 CvInstanceName Instance001 CvClientName magnum_SN

selectiveOnlineFull 1 CV_restCopyPrec 2 srcCrossClient sde-sap5

UNIX Configuration

The parameter file is located under the <software_install_folder>/SapMaxDbAgent.

numstreams 1 CvInstanceName Instance001 CvClientName magnum_SN

selectiveOnlineFull 1 CV_restCopyPrec 2 srcCrossClient sde-sap5

3. Verify that the backup tool is specified as BACKINT in the backup template if you intend to run
backup and restore jobs from the SAP Database Studio.
Configuring Multiple Streams for
Backups and Restores
 Updated Monday, November 13, 2023

When you run multiple stream database backups and restores for the SAP MaxDB iDataAgent, you must
define the path for each stream/pipe that is used for the storage media.

You must configure the SAP MaxDB parameter file (param) for both configurations to use multiple
streams backups and restores. For example if you define 2 pipe mediums for the backup devices, set the
numstreams parameter to 2.

Procedure

Windows Client

1. Log in to the database and run the following command from the dbm client interface:

dbmcli -d <database name> -u <UserName,Password>

Example

Parameter Value

Database Name cert1

User Name DBM

Password DBM

dbmcli -d cert1 -u DBM,DBM

2. Type the following commands to define the path for the stream/pipe:

You must use the following format:

\\. \pipe\[pipe name]

  Note

For each backup device, you must define two pipe mediums.

Example

Variable Description

BackData2 A vendor utility backup device that uses the DATA option and is used for full data
backups.

BackPages2 A vendor utility backup device that uses the PAGES option and is used for
incremental data backups.

BackLog A vendor utility backup device that uses the LOG option and is used for log
backups.

medium_put BackData2\mem1 \\.\pipe\pipe_mem1 PIPE DATA 0 0 NO NO '' BACK

medium_put BackData2\mem2 \\.\pipe\pipe_mem2 PIPE DATA 0 0 NO NO '' BACK
medium_put BackPages2\mem3 \\.\pipe\pipe_mem3 PIPE PAGES 0 0 NO NO '' BACK
medium_put BackPages2\mem4 \\.\pipe\pipe_mem4 PIPE PAGES 0 0 NO NO '' BACK
medium_put BackLog \\.\pipe\pipe_mem5 PIPE LOG 0 0 NO NO '' BACK medium_put
CompleteD G:\sdb\gb40\data\completeD FILE DATA 0 0 YES

UNIX Client

1. Log in to the database and run the following command from the dbm client interface:

dbmcli -d <database name> -u <UserName,Password>

Example

Parameter Value

Database Name cert1

User Name DBM

Password DBM
 bird:/opt/sdb# dbmcli -d cert1 -u DBM,DBM

2. Type the following commands to define the path for the stream/pipe:

 Note

For each backup device, you must define two pipe mediums.

You can specify any file path as a pipe and create the pipes in the operating system.

Example

Variable Description

BackData2 A vendor utility backup device that uses the DATA option and is used for full data
backups.

BackPages2 A vendor utility backup device that uses the PAGES option and is used for
incremental data backups.

BackLog A vendor utility backup device that uses the LOG option and is used for log
backups.

medium_put BackData2\m0 /opt/sdb/testdb/files/m0 PIPE DATA 0 0 NO NO '' BACK

medium_put BackData2\m1 /opt/sdb/testdb/files/m1 PIPE DATA 0 0 NO NO '' BACK
medium_put BackPages2\m2 /opt/sdb/testdb/files/m2 PIPE PAGES 0 0 NO NO ''
BACK medium_put BACKPages2\m3 /opt/sdb/testdb/files/m3 PIPE PAGES 0 0 NO NO
'' BACK medium_put BackLog\m0 /opt/sdb/testdb/files/m4 PIPE LOG 0 0 NO NO ''
BACK medium_put CompleteF /opt/sdb/testdb/data/complete FILE DATA 0 0 YES

Example

numstreams 2 CvInstanceName Instance001 CvClientName magnum_SN

Specifying the Media Parameters for SAP
MaxDB Command Line Operations
 Updated Monday, November 13, 2023

Command line backups use the storage policy and the data path specified in the CommCell Console
SAP MaxDB database instance by default.

You can override the default parameters by specifying media parameters file when you use the
CvOraSbtParams configuration parameter. This feature is supported for backup and restore database
operations.

When you configure this option on a database, the application command line backups use the media
parameter storage policy. You must associate the Data Path (MediaAgent, Library, Drive Pool) with the
specified storage policy in the parameters file. For information on the supported parameters, see
Supported SAP MaxDB Configuration File Parameters.

Procedure

1. Create a media parameters file with the required media parameters.

The parameter file format is:

[<Parameter Name-1>] <Value-1> < [<Parameter Name-2>] <Value-2>

Example

[sp] SAP_MAXDB [mediaagent] UNIXDB11 [library] LIB_MAXDB

2. Specify the CvOraSbtParams configuration parameter in the parameter file (param). You must
provide the full path to the media parameters file.

UNIX Example

The parameter file is located under the<software_install_folder>/SapMaxDbAgent directory.

 numstreams 1 CvInstanceName Instance001 CvClientName magnum_SN
CvOraSbtParams /opt/media_file

Windows Example

The parameter file is located under the <software_install_folder>\SapMaxDbAgent directory.

numstreams 1 CvInstanceName Instance001 CvClientName magnum_SN

CvOraSbtParams C:\media_file.txt
Configuring the Parameters for
CommCell Console Third-Party Job
Authentication
 Updated Monday, November 13, 2023

You can have the CommCell Console authenticate third party database backup and restore jobs to
ensure that the user has the correct credentials and has included a valid token file in the job request.

Procedure

1. Enable CommCell Console Authentication of Third Party Command Line Jobs.

2. Run the qlogin command with the token file option (-f) to obtain a token file from the SAP MaxDB
parameter file.

On the command line, go to Software_Installation_Directory/Base directory and type the following

command:

UNIX:

qlogin -u admin -f /opt/tokenfile

Type the password to log in successfully to the CommServe.

Windows:

QLogin.exe -u admin -f C:\tokenfile

Type in the password to log in successfully to the CommServe.

3. Create a token parameter text file that specifies the location of the token file that the qlogin
command created.

To see the token file contents, on the command line, type the following command, substituting
token_paremeter_file with the token parameter text file name.

cat token_parameter_file [CvQcmdTokenFile] token_file_location

 UNIX:

cat /opt/thirdpartytoken.txt [CvQcmdTokenFile] /opt/tokenfile

Windows:

C:\thirdpartytoken.txt [CvQcmdTokenFile] C:\tokenfile

4. For UNIX root installs, set the read permissions on the token file that the qlogin command created so
that application users can read the file.

Example:

If the token file name is "tokenfile", on the command line type the following:

chmod 644 /opt/tokenfile

5. Set the token file in the parameters file before you perform third-party command line backups and
restores.

Set the CvOraSbtParams parameter to the SAP MaxDB Agent parameter file.

CvOraSbtParamslocation_of_token_parm_file

UNIX:

CvOraSbtParams /opt/thirdpartytoken.txt

Windows:

CvOraSbtParams C:\thirdpartytoken.txt
Registering the Client in SAP SLD
 Updated Monday, November 13, 2023

After the installation, you can register the client Data Agent software in the SAP Software Landscape
Directory (SLD) as recommended by SAP.

This is an optional procedure that can be run on any SAP MaxDB client and can be used to register any
other client if needed.

Before You Begin

Verify that the minimum supported JRE version is installed. On the command line, type java -version .
If the version is lower than the minimum supported version, install the latest version of Java.

Java SE Platform

The software supports Java 11.

Procedure
1. Create an XML File using the backint program:

On Windows Client:

Run the backint program from a command prompt in the base directory as the domain
administrator.

backint <-f createsldxml> <short_client_name> <maxdb>

Example:

backint -f createsldxml racer maxdb

On Unix Client:

Run the backint program as a root user and in the <iDataAgent> directory.

[root@flyhat3 iDataAgent]# . ../Base/cvprofile [root@flyhat3 iDataAgent]#

../SapMaxDbAgent/backint -f createsldxml racer maxdb
2. Run the adjacent command.

A return code of 200 implies a successful registration of SAP for Oracle client racer in the SLD.

java -cp sldreg.jar sldreg <SLD_HOST_NAME> <PORT_NUMBER> <USER_NAME>

<PASSWORD> <XML_FILE> Example: # java -cp sldreg.jar sldreg 155.56.49.26 80
3rd_party isvconnect08 racer_maxdb.xml Retcode:200
For more information about Commvault® softwaremodules and solutions,
and for up-to-date system requirements, please contact us:
www.commvault.com | 888.746.3849 | get-info@commvault.com

CommvaultWorldwide Headquarters
1 Commvault Way | Tinton Falls, NJ07724 | Phone: 888.746.3849 | Fax: 732.870.4525

Commvault Regional Offices

United States | Europe | Middle East & Africa | Asia-Pacific | Latin America & Caribbean | Canada | India | Oceania