Adint Install (Maxdb)

'Best Practices for ADINT/TSM Installation and Configuration'
Best Practices:
ADINT/TSM
Installation and Configuration
by
Rainer Diederichs
IBM Deutschland Research & Development GmbH
Boeblingen
30 September 2012
Copyright IBM Corporation, 2012
Copyright International Business Machines Corporation 2012. All rights reserved.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system
without prior written permission of IBM Corporation. IBM Corporation grants you limited
permission to make hardcopy or other reproductions for your own use, provided that each such
reproduction shall carry the IBM Corporation copyright notice.
This information could include technical inaccuracies or typographical errors.
Trademarks
IBM, AIX, FlashCopy, Power and Tivoli are registered Trademarks of IBM Corporation in the United
States and other countries
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in
the United States, other countries, or both.
SAP, SAP MaxDB, R/3, APO, LiveCache are trademarks or registered trademarks of SAP AG
UNIX is a registered trademark of The Open Group in the United States and other countries.
Table of contents
A
A.1
A.2
A.3
Set-up/Overview
Preinstallation
TSM server
5
7
7
A1.1
A1.2
A1.3
A1.4
A1.5
7
7
7
7
8
target TSM server

node name
storage
backup data retention
node password
TSM API Client

ADINT/TSM
A.3.1 ADINT/TSM
A.3.2 ADINT/TSM
8
executables
configuration files
8
8
9
9
A.4
SAP MaxDB
B.
ADINT/TSM installation
11
B1.1
11
11
11
11
11
11
11
B1.2
Modes of installation
B1.1.1 silent installation
B1.1.2 console installation
types of installation
B1.2.1 first time installation
B1.2.2 upgrade installation from release 2.3.X
B1.2.3 update installation within release 2.4
B.2 Steps of the ADINT/TSM Installation Program
12
C. Postinstallation
13
C1.1 ADINT/TSM profile

C1.2 TSM profiles - Windows
C1.2.1 Server Options file
C1.2.2 the directory DSMI_CONFIG
C1.2.3 set DSMI_* system variables
C1.3 TSM profiles - UNIX
C1.3.1 Client System Options file dsm.sys
C1.3.2 Client System Options file dsm.opt
13
15
15
15
15
16
16
16
C2. Customizing SAP MaxDB
17
C2.1 For Windows

C2.1.1 define pipes for data transfer
C2.2 For UNIX
C2.2.1 define ADINT and ADA_OPT variables in the database
C2.2.2 define pipes for data transfer
C3 TSM Password and ADINT usage key input
C3.1 TSM password authentication - Passwordaccess Prompt
C3.2 TSM password authentication - Passwordaccess Generate
C3.3 ADINT Usage Key
17
17
18
18
18
19
19
19
19
Change History:
2012-09-13 p. 17 para C2.1.1
corrected command syntax
Dear reader,
we appreciate your feedback.
Please send us your comments or suggestions to
backint@de.ibm.com
Set-up Overview
ADINT/TSM is an intelligent interface program consisting of 2 executables
adint2, the intelligent controler
adintagent, the multithreaded data mover
These executables are placed in the installation path pointed to by an environment/system variable
ADINT.
ADINT/TSM serves two interfaces, SAP MaxDB as well as Tivoli Storage Manager (TSM), and
therfore needs configuration parameters for both. Since ADINT/TSM is an intelligent interface
program, it uses an additional set of configuration parameters to control its own operation.
Configuration parameters are contained in 2 configuration files
init<SID>.utl (edible)
internparamfile.adi (non-edible passwords/keys)
to be placed in the configuration path pointed to by an environment/system variable ADA_OPT.
On the TSM side ADINT connects to the TSM Client API for communication with the TSM server.
The TSM API has its own executables and configuration files, which are placed in standard paths
during the TSM client install process. For this description we assume a standard TSM installation.
All relevant files/executables with their paths and owners are shown in table 1 for a Windows and
UNIX environment.
Topic
full path name

files
env. variable owner
Table
1
Key
paths/directories
and
files
for
ADINT/TSM
set-up
ADINT/TSM paths/directories
Windows
install path
\Program Files\Tivoli\TSM\adint
configuration path \maxdb\adint
adint2.exe
ADINT
adintagent.exe
init<SID>.utl
ADA_OPT
internparamfile.adi
'system'
'system'
UNIX
install path
/usr/tivoli/tsm/adint64 (AIX)
/opt/tivoli/tsm/adint64 (other UNIX)
configuration path /maxdb/adint
adint2
ADINT
adintagent
init<SID>.utl
ADA_OPT
internparamfile.adi
<MaxDB
Instance owner>
<MaxDB
Instance owner>
TSM Client paths/directories

Windows
install path
\Program Files\Common Files\Tivoli\TSM\api64
configuration path \maxdb\adint

log path
UNIX
\maxdb\adint
apienu.dll
dscenu.txt
dsm.opt
<server>.opt
dsierror.log
/usr/tivoli/tsm/client/api/bin64 (AIX)
/opt/tivoli/tsm/client/api/bin64 (other UNIX)
/usr/tivoli/tsm/client/api/bin64 (AIX)
configuration path
/opt/tivoli/tsm/client/api/bin64 (other UNIX)
libApiTSM64.a
EN_US
dsm.opt
link to dsm.sys
log path
dsierror.log
install path
/maxdb/adint
DSMI_DIR
'system'
DSMI_CONFIG
'system'
DSMI_LOG
default
preset
default
preset
errorlogname dsm.sys - server

entry in dsm.sys selected by dsm.opt
Note: TSM client has 2 sets of environment variables named DSM_ for b/a client and DSMI_for api
client.
On the database side ADINT/TSM connects to a pipe interface, which will be customized through
database commands (dbmcli) following the installation of ADINT/TSM.
In the following we will describe the complete ADINT/TSM setup process in 3 steps
preinstallation (configuration of ADINT/TSM, API and TSM server)
installation of ADINT/TSM (installer)
postinstallation (customizing ADINT/TSM and TSMand SAP MaxDB interfaces)
Sample names used throughout the document are shown in italic letters.
Recommendations/explanations to various topics are placed in boxes.
A. Preinstallation
A.1 TSM server
Define
A1.1 target TSM server, e.g. > server_a
A1.2 node name, e.g. maxdb_T01
This node name defines a client with its assigned TSM server resources.
We recommend to define within a database server a dedicated node for a MaxDB instance to
A1.3
storage
needed specific
as backup
repository
(management
classes).
keep
the database
definitions
separate
from those
of other components and avoid
MaxDB
offers
3
types
of
backups
for
which
specific
media
inadvertent changes. We also recommend to use a node name, pools
which can
linksbe
theselected,
node to e.g.
the SID,
full database backup
> mgmtclass_a
e.g.maxdb_<SID>,
to better
identify related(tape)
information.
incremental database backup > mgmtclass_b (can be same as full backup) (tape/disk)
log backup > mgmtclass_c (disk or disk-tape hierarchical)
storage selection should be based on data volume: tape for large chunks of data, disk for
segemented data like logs. Hierarchical storage pools (disk-tape) are optimum for log backups
(server internal disk-tape migration)
selected managementclasses must have an archive copygroup defined
the number of mount points, i.e. physical tape drives, must at minimum be equal to the
number of parallel sessions
separate management classes are strongly recommended for data and log backups to
protect against media failures.
different management classes for the 2 log copies should be defined if the dual log copy
function is activated
A1.4 Backup data retention
Selection can be made between TSM server based retention (per backup object) or
ADINT/TSM based retention (per backup generation).
> TSM: RETVER=20 ADINT/TSM (init<SID>.utl): MAX_VERSIONS 0
TSM expires each object individually n days after it is checked in by RETVER= n|unlimited..
ADINT/TSM expires complete backup generations (full data backup plus susequent
incremental and log backups) within a specified retention threshhold by MAX_VERSION n.
A new version number is assigned each time a full backup has completed successfully.
The ADINT/TSM method is to be preferred if full backup cycles are irregular or longer (several
days).
Only one method should be activated at a time for a predictible process.
e.g. TSM expiration:
RETVER=20 > MAX_VERSION 0
ADINT/TSM expiration:
MAX_VERSION 20 > RETVER=unlimited
A1.5 node password

Access to a node should be controlled by a password. Authentication is activated on the
TSM server by the TSM adminstrator. TSM offers 2 options for authentication of a node:
PASSWORDACCESS PROMPT (default setting) or PASSWORDACCESS GENERATE.
The password is used by ADINT/TSM automatically with every call to TSM.
The 'prompt' option is used when the password is changed infrequently and recommended for
Table
settings for The
TSMpassword
passwordwill
handling
testing because
of 2itsParameter
simpler configuration.
be stored by ADINT/TSM.
The 'generate' option should be used when the security policy calls for frequent password
A.2
TSM API
changes,
e.g.Client
in 60 or 90 days intervals.
For a new installation, the password must be the same as was spedified when the node
Check
that 64 bit to
executables
are installed
andmust
in the
right
table
1. server, then
was registered
TSM. A password
change
first
be path,
done see
on the
TSM
for ADINT/TSM using the manual command adint2 -x..
Password handling requires certain combinations of parameter settings which are shown in
A.3
theADINT/TSM
following table:
The
set up for ADINT/TSM
deals with 2 classes ofPW
objects.
Profile
Parameter
stored by ADINT PW stored by TSM API
UNIX:
dsm.sys in the install
PASSWORDACCESS
PROMPT
GENERATE
A3.1
Executables
path
1)
PASSWORDDIR
n.a.
<path>
The installer will create the install path and copy into it executables
as well as configuration
NODENAME
n.a.
<nodename>
file and script file samples, User Guide and Readme.
Windows:
<server>.opt
PASSWORDACCESS
PROMPT
GENERATE
environment
variable
ADINT = <install path>
NODENAME
n.a.
<nodename>
ADINT/TSM
profileto leave
PASSWORDREQUIRED
NO1. This will help us
We recommend
the default name used YES
by the installer, see table
init<SID>.utl
NODENAME
<nodename>
n.a.
with remote trouble shooting.
(each serverstatement)
1) The MaxDB instance owner must have read and write permission for the specified path
A3.2 Configuration files in the configuration path

The configuration path must be created manually, the installer with place the copies of the
ADINT/TSM configuration file samples init<SID>,utl and internparamfile.adi into it.
environment variable ADA_OPT = <configuration path>
We strongly recommend to use 2 different paths for executables and configuration files. This
way the original configuration files with their default values can be retained in the install path
and used later for a reset of the actual configuration files.
We also recommend to create the configuration path in the SAP MaxDB directory to keep
configuration data and logs for ADINT/TSM together with related SAP MaxDB data for
consistency and convenience of trouble shooting. The API error log should be placed there as
well.
A.4 SAP MaxDB

Collect the following information for use later in the install process:
name of the server hosting the MaxDB
system ID of the MaxDB to be backed up
MaxDB instance owner name and password
MaxDB database administrator name and password
At the end of the preinstall step you should have a verified list of key parameters values required
for the installation and subsequent postinstall steps. The responsible administrators should be
involved wherever necessary to make sure the data is complete and current..
We recommended to enter the actual values into the list below to be used as source during
installation as well as documentation of the environment for later reference.
Parameter
sample
value
use required for

for 1st time inst.
required for
upgrade inst.
required for
update inst.
SAP MaxDB
server name
<dbserv>
C2.1 X
C2.2
SAP MaxDB SID

instance name
<SID>
B2- X
#5
C2.1
SAP MaxDB
instance owner name
<instance
owner>
B2
#6
Instance owner
password
C2.2 X
SAP MaxDB
administrator name
<dbm_user>
C2.1 X
C2.2
admin password
<dbm_pwd>
C2.1 X
C2.2
ADINT/TSM usage key

not requ. for 60 day trial
<usage key>
C3.3 X
ADINT/TSM installation
directory
OS specific,
see fig. 1
B2- X, default
#3
C2.1
ADINT/TSM
configuration directory
OS specific,
see fig. 1
B2- X
#4
C2.2
TSM client API 64 bit

installation directory
OS specific,
see fig. 1
X, default
TSM server name
<server_a>
B2
#7
TSM node name
<maxdb_<SID>> B2
#7
TSM node password
<node pwd>
C3.1 X
C3.2
TSM mgmt class for full

database backup
<mgmtclass_a> B2
#7
TSM mgmt class for

incremental db backup
<mgmtclass_b> B2
#7
TSM mgmt class for log

backup
<mgmtclass_c> B2
#7
Table 3 List of key parameters for ADINT/TSM set-up
10
B. ADINT/TSM Installation
B1.1 Modes of installation
The installer supports 2 special installation modes
B1.1.1 Silent installation
The installation options must be recorded at first in a response file by issuing
<ADINT/TSM installation package> -DRECORDFILE=<record filename>
The installation options in the response file are stored in human-readable format and can be
modified if the silent install process is to be repeated on different systems with, for example,
different SAP MaxDB SIDs.
The silent installation function is then started with the response file
<ADINT/TSM installation package> -i silent -f <record filename>
B1.1.2 Console installation
For target systems that do not have a window manager, the setup program supports an
installation in console mode.
Console mode suppresses the graphical wizard panels of a GUI installation and displays data
entered and messages on the console or in a command prompt window.
To start console install specify the following command:
<ADINT/TSM installation package> -i console
Installation options can also be recorded in console mode for use as response file of a silent
installation
<ADINT/TSM installation package> -i console -DRECORDFILE=<record filename>
B1.2 Types of installation

To preserve as much as much of existing configuration information as possible you will be asked at
the start of the installation which type you want to perform:
B1.2.1 first time installation
The installation program will perform a configuration from scratch including a very basic connection
to the TSM server.
B1.2.2 upgrade installation from release 2.3.X or below
The installation program will preserve all existing setup and configuration information except for
parameters in the internparamfile.adi, which will be replaced with a new one. Therefore the
ADINT/TSM usage key (and TSM password for PASSWORDACCESS PROMPT) will have to be
input with the manual command adint2 -l (and adint2 -x TSM password) during postinstallation.
The version count will be restored with the next access to the TSM server.
B1.2.3 update installation within release 2.4
The installation program will preserve all existing set up and configuration information and only
replace files in the installation path.
11
B.2 Steps of the ADINT/TSM Installation Program

The screens for the interactive installation are shown in below table. Which screens will be used
depends on the platform and installation type selected.
Nr. Topic
1
2
3
4
5
6
UNIX/
Windows
Used with
Inst. type
both
all
both
all
installer will set-up and copy executables
both
all
as set-up by user
installer will copy internparamfile.adi
both
first time
upgrade
installer will copy .init<SID>.utl to

configuration path and rename
both
first time
installer will update this user's

environment variables with install and
config path
UNIX only
1)
first time
installer will update entries in the

init<SID>.utl
both
first time
overview of actual patameters
both
all
both
all
both
all
Action
start screen
list of required input parameters
type of installation selection

first time / upgrade / update
path configuration
define installation path
path definition
identify configuration path
data base ID
identify SAP MaxDB SID
SAP MaxDB instance owner

identify user name
basic TSM configuration

identify TSM server/node name
and management classes used
preinstallation summary
installation process running
10 finish screen
Table 4 Screen overview for interactive installation
Notes: 1) for Windows platforms the installer will enter these variables as system variables
12
C. Postinstallation tasks
Post installation tasks include
completing the configuration in various profiles, ADINT and TSM
defining ADINT to SAP MaxDB (definition of backup media, set-up of pipes)
setting TSM password and ADINT usage key
C1.1 ADINT/TSM profile
The ADINT/TSM configuration parameters are stored in the init<SID>.utl file in the path defined by
the variable ADINT.
When the option 'first time installation', i.e. Try and Buy or a new instance, has been selected for
the install process, the installer will place a copy of the sample profile from the install package to
the configuration directory. For an upgrade or update installation the existing profiles will stay
untouched.
The parameters of the init<SID>.utl profile in the configuration path of ADINT must now be
adapted to the specific configuration.
Parallel session control

The number of parallel data transfers between the database and TSM is determined by SAP
MaxDB through definition of a number of pipes, see chapter C2.1.2.
The sessions can be different for full, update (incremental) and log backups/restores.
The management class used by a TSM server for a specific backup/restore must provide a
number of mount points (tape or sequential file media) at least equal to the number of
corresponding SAP MaxDB pipes, else the action will result in an error.
The parameters FULLSESSIONS, UPDATESESSIONS and LOGSESSIONS in the server
statements of the ADINT profile determine how many sessions are to be opened for each of
the TSM servers to be used.
The database will still use all its defined pipes for a backup/restore, even if their number is
higher than the sum of the sessions defined in the server statement(s) of the ADINT profile.
13

#----------------------------------------------------------------------------# Sample Profile for ADINT/TSM for Windows, see note below
----------------------------------------------------------------------------#----------------------------------------------------------------------------# Range: 0-32768 ('0' means all versions will be kept)
#----------------------------------------------------------------------------MAX_VERSION 3
#----------------------------------------------------------------------------# Range: 0-200 ('15' is a good default, change only on hotline request)
#-----------------------------------------------------------------------------
TRACE 15
#----------------------------------------------------------------------------# This is where the ADINT/TSM logfile will be written to.
# Name can be user defined,e.g. c:\maxdb\adint\adint2.log
#----------------------------------------------------------------------------LOGFILE <drive>:\<path>\<filename>
#----------------------------------------------------------------------------# Range: 0-1048576 (size (Byte) of the data transfer buffer for ADINT/TSM
# and TSM API)
#-----------------------------------------------------------------------------
BUFFERSIZE 32768
#--------------------------------------------------------------------# Range: 1-2 (specifies the number of log copies created by ADINT/TSM)
#--------------------------------------------------------------------REDOLOGCOPIES 1
#----------------------------------------------------------------------------# Statements for each TSM server(s) to be used. One server section must be
# customized properly, additional sections are only required when using the
# 'alternate/multiple server' capability, see app. D of the ADINT User Guide
#----------------------------------------------------------------------------SERVER <server_a>
# TSM servername (max. 64 chars.)
NODENAME <maxdb_<SID>>
# TSM nodename (max. 64 chars.)
PASSWORDREQUIRED yes
# use a TSM password
FULLSESSIONS 4
# TSM sessions (full backup)
UPDATESESSIONS 2
# TSM sessions (incr. backup)
LOGSESSIONS 1
# TSM sessions (log backup)
FULLMANAGEMENTCLASS <mgmtclass_a>
# TSM mgmtclass (full backup)
UPDATEMANAGEMENTCLASS <mgmtclass_b>
# TSM mgmtclass (incr. backup)
LOGMANAGEMENTCLASS <mgmtclass_c>
# TSM mgmtclass (log backup)
#SERVER <server_b>
# TSM servername (max. 64 chars.)
# NODENAME <maxdb_<SID>>
# TSM nodename (max. 64 chars.)
# PASSWORDREQUIRED yes
# use a TSM password
# FULLSESSIONS 4
# TSM sessions (full backup)
# UPDATESESSIONS 2
# TSM sessions (incr. backup)
# LOGSESSIONS 1
# TSM sessions (log backup)
# FULLMANAGEMENTCLASS <mgmtclass_d>
# TSM mgmtclass (full backup)
# UPDATEMANAGEMENTCLASS <mgmtclass_e> # TSM mgmtclass (incr. backup)
# LOGMANAGEMENTCLASS <mgmtclass_f>
# TSM mgmtclass (log backup)
#----------------------------------------------------------------------------# End of profile
Note: The ADINT profile for UNIX is identical to the Windows one above, except for the following
parameters
LOGFILE /<path>/<filename>
BUFFERSIZE 131072
14
C1.2 TSM profiles Windows

C1.2.1 Server Options file
ADINT/TSM obtains information for each assigned TSM server from a corresponding profile
<server>.opt in the directory defined by variable DSMI_CONFIG. The example for this file shown
below can be copied from the ADINT installation path
************************************************************************
* Tivoli Distributed Storage Manager
*
* Sample Server Options file SERVER.OPT, see the TSM doc for details
*
************************************************************************
COMMmethod TCPIP
NODEname maxdb_<SID>
TCPPort 1500
TCPServeraddress xxx.xxx.xxx.xxx
PASSWORDACCESS PROMPT
TCPBUFFSIZE 31
TCPWINDOWSIZE 32
DISKBUFFSIZE 32
The buffersizes above are performance relevant parameters. The values shown reflect what we
normally use in our test environments.
C1.2.2 The directory designated by DSMI_CONFIG must also contain a file dsm.opt, although this
file is not used by ADINT/TSM. The example for this file shown below can be compied from the
ADINT installation path. Absence of this file will cause an error.
************************************************************************
*
* Sample TSM User Options file DSM.OPT for Windows,ADINT/TSM), see the *
* TSM documentation for details.
*
************************************************************************
*ErrorLogName c:\maxdb\adint\tsmapierror.log
Recommendation:
There are 2 ways to define the api errorlog, in the dsm.opt or as system variable DSMI_LOG.
It is recommende to use just one alternative. We prefer the use of a system variable as this
definition is system-wide and requires only 1 entry.
Note:
The standard Tivoli Storage Manager client also uses a file dsm.opt, but this TSM standard client
user option file is located in the path set by the variable DSM_CONFIG.
C1.2.3 Set DSMI_* system variables
Add as system variables, see Table 1
DSMI_DIR
C:\Program Files\Common Files\Tivoli\TSM\api64
DSMI_CONFIG
C:\maxdb\adint\dsm.opt
DSMI_LOG
C:\maxdb\adint
15
C1.3 TSM profiles UNIX

C1.3.1 Client System Options file
The dsm.sys includes a collection of connection parameter definitions for TSM servers which can
be accessed by a client system. This sample is available as file in the ADINT installation directory.
************************************************************************
* Sample for ADINT/TSM specific section for client system options
*
* definition of dsm.sys for UNIX
*
************************************************************************
Servername server_a
COMMmethod TCPip
TCPPort 1500
TCPServeraddress xxx.xxx.xxx.xxx
TCPBuffsize 32
TCPWindowsize 24
ErrorLogName /maxdb/adint/tsmapierror.log
Servername server_b
COMMmethod TCPip
TCPPort 1500
TCPServeraddress yyy.yyy.yyy.yyy
TCPBuffsize 32
TCPWindowsize 24
ErrorLogName /maxdb/adint/tsmapierror.log
C1.3.2 Client System Options file

The dsm.opt identifies the server to be used for this client. The example for this file shown below
can be copied from the ADINT installation path
************************************************************************
*
* Sample Client User Options file dsm.opt for UNIX
*
************************************************************************
Servername server_a
Tapeprompt No
Note:
The dsm.sys as a system-wide file should be accessed through a link. For the application specific
dsm.opt we recommend a physical copy in the designated path, see table 1.
16
C2. Customizing SAP MaxDB

C2.1 For Windows
ADINT and ADA_OPT variables have already been set during installation.
C2.1.1 Define pipes for data transfer

Data are exchanged between SAP MaxDB and TSM (via ADINT/TSM) through pipes. Each pipe
represents an individual data stream between the database and the storage manager.
It corresponds to a session in TSM terms. Parallel sessions require definition of multiple pipes.
Different pipes can be defined for different types of backups - DATA (full), PAGES (incremental) and
LOG (log).
Logon as dbm user with the option -uUTL
dbmcli -d <SID> -n <dbserv> -u <dbm_user>,<dbm_pwd> -uUTL
and define each pipe with the cli command
medium_put <media ID> <location> PIPE <bkp_type> 0 8 NO NO \\ TSM
where
<media ID> is the name of the backup medium
<location> name of the device/file with which it can be addressed through operating system functions
<bkp_type> the type of backup using this medium, possible values are: DATA, PAGES, LOG
Examples
- log backup single medium for 1 session
medium_put TSM_LOG \\.\pipe\p01_log PIPE LOG 0 8 NO NO \\ TSM
- full backup single medium for 1 session
medium_put TSM_DATA \\.\pipe\p01_data PIPE DATA 0 8 NO NO \\ TSM
- full backup multiple media for 2 sessions
medium_put TSM_PARA\SESS1 \\.\pipe\p01_data1 PIPE DATA 0 8 NO NO \\ TSM
medium_put TSM_PARA\SESS2 \\.\pipe\p01_data2 PIPE DATA 0 8 NO NO \\ TSM
17
C2.2 For UNIX
C2.2.1 Define ADINT and ADA_OPT variables in the database

The variables ADINT (installation path) and ADA_OPT (fully qualified file name for ADINT profile
init<SID>.utl) must be defined for the dbm_user environment.
As instance owner issue the following command to log on to the database
and for each variable issue the cli command
dbm_configset -raw <variable> <value>
Example:
dbmcli -d P01 -n dbserv1 -u dbm,dbmpwd -uUTL
dbm_configset -raw ADINT /usr/tivoli/tsm/adint64
dbm_configset -raw ADA_OPT /maxdb/adint/initP01.utl
C2.2.2 Define pipes for data transfer

Data are exchanged between SAP MaxDB and TSM (via ADINT/TSM) through pipes. Each pipe
represents an individual data stream between the database and the storage manager. It
corresponds in TSM terms to a session. Parallel sessions require definition of multiple pipes. Pipes
can also be defined specifically for different types of backups DATA (full), PAGES (incremental)
and LOG (log).
Logon as dbm user with the option -uUTL
and define each pipe with the cli command
medium_put <media ID> <location> PIPE <bkp_type> 0 8 NO NO \\ TSM
where
<media ID> is the name of the backup medium
<location> name of the device/file with which it can be addressed through operating system functions
<bkp_type> the type of backup using this medium, possible values are: DATA, PAGES, LOG
Examples
- log backup single medium for 1 session
medium_put TSM_LOG /tmp/p01_log PIPE LOG 0 8 NO NO \\ TSM
- full backup single medium for 1 session
medium_put TSM_DATA /tmp/p01_data PIPE DATA 0 8 NO NO \\ TSM
- full backup multiple media for 2 sessions
medium_put TSM_PARA/SESS1 /tmp/p01_data1 PIPE DATA 0 8 NO NO \\ TSM
medium_put TSM_PARA/SESS2 /tmp/p01_data2 PIPE DATA 0 8 NO NO \\ TSM
18
C3 TSM Password and ADINT usage key input

C3.1 TSM password for Passwordaccess Prompt
The TSM password is set via the manual ADINT command adint2 -x. This will start a dialogue, at
the end of which the password is stored in the binary file interparamfile.adi in the configuration
path. If multiple servers are defined in the init<SID>.utl, you will be prompted for a password for
each server.
C3.2 TSM password for Passwordaccess Generate
When PASSWORDACCESS GENERATE is active, you must have root authority to set the TSM
password. You can then choose between 2 alternatives
- use adint2 -x, which requires setting the ADINT variables for root as well
If multiple servers are defined in the init<SID>.utl, you will be prompted for a password for each
server.
- use the TSM command line dsmc -se=<server name> starting a TSM client dialog.
If multiple servers are defined in the init<SID>.utl, you must issue the dsmc command for each
server.
With PASSWORDACCESS GENERATE the password is not stored in the internparamfile.adi.
After having set the TSM password you can check the connection to the TSM server with the
manual command adint2 -q. For more details see chapter 4.1.
Note: in order to get a list of the manual ADINT commands pls type adint2 -h
C3.3 ADINT Usage Key
The usage key disables expiration and enables the parallelism capability of ADINT. It is a 9 position
alphanumeric string, which is input via the manual command adint2 -l and stored in the
internparamfile.adi.
Starting with release 2.4.3 the usage key can also be set via a program using the ADINT command
adint2 -l -k <usage key>
to enable customers with a large number of ADINT copies to change the usage key by program
instead of manual input.
C4 Quick Function Test

C4.1 Validation of the ADINT/TSM to TSM connection
You can perform a quick check of the proper definitions for the communication between
ADINT/TSM and TSM by issuing the manual ADINT/TSM command
adint2 -q
for a query of the backup repository. If the set-up is OK, TSM should return a list of objects (empty
or populated).
19
C4.1Validation of the ADINT/TSM to SAP MaxDB connection

4.1.1 Backup of a test file
As instance owner use the manual ADINT/TSM backup command
adint2 -b -n SAVEDATA1 -p <testfile>
where <testfile> is the fully qualified name of a file for testing
followed by the c
to backup a small test file to TSM.
With adint2 -q you can susequently check whether the file is included in the backup repository.
20

Adint Install (Maxdb)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Adint Install (Maxdb)

Uploaded by

Copyright:

Available Formats

'Best Practices for ADINT/TSM Installation and Configuration'

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

Copyright International Business Machines Corporation 2012. All rights reserved.

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

target TSM server

TSM API Client

B.2 Steps of the ADINT/TSM Installation Program

C1.1 ADINT/TSM profile

C2. Customizing SAP MaxDB

C2.1 For Windows

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

corrected command syntax

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

full path name

configuration path \maxdb\adint

configuration path /maxdb/adint

TSM Client paths/directories

\Program Files\Common Files\Tivoli\TSM\api64

configuration path \maxdb\adint

Copyright IBM Corporation, 2012

errorlogname dsm.sys - server

'Best Practices for ADINT/TSM Installation and Configuration'

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

A1.5 node password

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

A3.2 Configuration files in the configuration path

A.4 SAP MaxDB

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

use required for

SAP MaxDB SID

ADINT/TSM usage key

TSM client API 64 bit

TSM server name

TSM node name

TSM mgmt class for full

TSM mgmt class for

TSM mgmt class for log

Table 3 List of key parameters for ADINT/TSM set-up

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

B1.2 Types of installation

Copyright IBM Corporation, 2012

'Best Practices for ADINT/TSM Installation and Configuration'

B.2 Steps of the ADINT/TSM Installation Program

installer will set-up and copy executables

installer will copy .init<SID>.utl to

installer will update this user's

installer will update entries in the

overview of actual patameters

type of installation selection

SAP MaxDB instance owner

basic TSM configuration

installation process running

Copyright IBM Corporation, 2012