Best Practices: ADINT/TSM Installation and Configuration

Transcription

1 Best Practices: ADINT/TSM Installation and Configuration by Rainer Diederichs IBM Deutschland Research & Development GmbH Boeblingen Revision 2 Copyright IBM Corporation,

2 Copyright International Business Machines Corporation 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 Server, 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. Copyright IBM Corporation,

3 Table of contents Set-up/Overview 5 A Preinstallation 7 A1 TSM server 7 A1.1 target TSM server 7 A1.2 node name 7 A1.3 storage 7 A1.4 backup data retention 7 A1.5 node password 8 A2 TSM Client API 8 A3 ADINT/TSM 8 A.3.1 ADINT/TSM executables 8 A.3.2 ADINT/TSM configuration files 9 A4 SAP MaxDB 9 B ADINT/TSM Installation 11 B1 Modes of installation 11 B1.1 silent installation 11 B1.2 console installation 11 B2 Types of installation 11 B2.1 first time installation 11 B2.2 upgrade installation from release 2.3.X 11 B2.3 update installation within release B3 Steps of the ADINT/TSM Installation Program 12 C Postinstallation 13 C1 Sample Profiles 13 C1.1 ADINT/TSM profile 13 C1.2 TSM profiles - Windows 15 C1.2.1 Server Options file 15 C1.2.2 the directory DSMI_CONFIG 15 C1.2.3 set DSMI_* system variables 16 C1.3 TSM profiles - UNIX 17 C1.3.1 Client System Options file dsm.sys 17 C1.3.2 Client System Options file dsm.opt 17 C2 Customizing SAP MaxDB 18 C2.1 For Windows 18 C2.1.1 define pipes for data transfer 18 C2.2 For UNIX 19 C2.2.1 define ADINT and ADA_OPT variables in the database 19 C2.2.2 define pipes for data transfer 19 C3 TSM Password and ADINT usage key input 20 C3.1 TSM password authentication - Passwordaccess Prompt 20 C3.2 TSM password authentication - Passwordaccess Generate 20 C3.3 ADINT Usage Key 20 D Quick Function Tests 21 D1 Validation of the ADINT/TSM to TSM connection 21 D2 Validation of the ADINT/TSM to SAP MaxDB connection 21 Copyright IBM Corporation,

4 Dear reader, we appreciate your feedback. Please send us your comments or suggestions to Copyright IBM Corporation,

5 Set-up Overview ADINT/TSM is an intelligent interface program consisting of 2 executables adint2, the intelligent controller adintagent, the multithreaded data mover These executables are placed in the installation path pointed to by an environment/system variable ADINT/TSM. ADINT/TSM serves two interfaces, SAP MaxDB as well as Tivoli Storage Manager (TSM), and therefore 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. All configuration parameters are contained in 2 configuration files init<sid>.utl (editable) internparamfile.adi (non-editable passwords/keys) to be placed in the configuration path pointed to by an environment/system variable ADA_OPT. For communication with the TSM server ADINT/TSM connects to the TSM Client API, which has its own executables and configuration files, 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 Windows and UNIX environments. Topic full path name files env. variable owner ADINT/TSM paths/directories Windows install path \Program Files\Tivoli\TSM\adint adint2.exe adintagent.exe ADINT 'system' configuration path \maxdb\adint init<sid>.utl internparamfile.adi ADA_OPT 'system' UNIX install path /usr/tivoli/tsm/adint64 (AIX) adint2 <MaxDB ADINT /opt/tivoli/tsm/adint64 (other UNIX) adintagent Instance owner> configuration path /maxdb/adint init<sid>.utl <MaxDB ADA_OPT internparamfile.adi Instance owner> TSM Client paths/directories Windows install path \Program Files\Common Files\Tivoli\TSM\api64 apienu.dll dscenu.txt DSMI_DIR 'system' configuration path \maxdb\adint dsm.opt <server>.opt DSMI_CONFIG 'system' log path \maxdb\adint dsierror.log DSMI_LOG UNIX install path /usr/tivoli/tsm/client/api/bin64 (AIX) libapitsm64.a /opt/tivoli/tsm/client/api/bin64 (other UNIX) EN_US default preset configuration path /usr/tivoli/tsm/client/api/bin64 (AIX) dsm.opt /opt/tivoli/tsm/client/api/bin64 (other UNIX) link to dsm.sys default preset log path /maxdb/adint dsierror.log errorlogname dsm.sys - server entry in dsm.sys selected by dsm.opt Table 1 Key paths/directories and files for ADINT/TSM set-up Copyright IBM Corporation,

6 Note: TSM Client has 2 sets of environment variables named DSM_ for the b/a client and DSMI_ for the client api. 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, TSM Client API and TSM Server) installation of ADINT/TSM (installer) postinstallation (customizing ADINT/TSM and TSM and SAP MaxDB interfaces) Sample names used throughout the document are shown in italic letters. Recommendations/explanations to various topics are placed in boxes. Copyright IBM Corporation,

7 A. Preinstallation A1 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 keep the database specific definitions separate from those of other components and avoid inadvertent changes. We also recommend to use a node name, which links the node to the SID, e.g. maxdb_<sid>, to better identify related information. A1.3 storage needed as backup repository (management classes). MaxDB offers 3 types of backups for which specific media pools can be selected, e.g. full database backup > mgmtclass_a (tape) 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 segmented 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 subsequent incremental and log backups) within a specified retention threshold 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 Copyright IBM Corporation,

8 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 testing because of its simpler configuration. The password will be stored by ADINT/TSM. The 'generate' option should be used when the security policy calls for frequent password changes, e.g. in 60 or 90 days intervals. For a new installation, the password must be the same as was spedified when the node was registered to TSM. A password change must first be done on the TSM server, then for ADINT/TSM using the manual command adint2 -x. Password handling requires certain combinations of parameter settings which are shown in the following table: Profile Parameter PW stored by ADINT PW stored by TSM API UNIX: dsm.sys Windows: <server>.opt ADINT/TSM profile init<sid>.utl (for each server statement) PASSWORDACCESS PASSWORDDIR 1) NODENAME PASSWORDACCESS NODENAME PASSWORDREQUIRED NODENAME PROMPT n.a. n.a. PROMPT n.a. YES <nodename> GENERATE <path> <nodename> GENERATE <nodename> NO n.a. 1) The MaxDB instance owner must have read and write permission for the specified path A2 TSM Client API Table 2 Parameter settings for TSM password handling Check that 64 bit executables are installed and in the right path, see table 1. We strongly recommend to use the default path set by a standard TSM installation. A3 ADINT/TSM The set up for ADINT/TSM deals with 2 classes of objects. A3.1 Executables in the install path The installer will create the install path and copy into it executables as well as configuration file and script file samples, User Guide and Readme. environment variable ADINT = <install path> We recommend to leave the default name used by the installer, see table 1. This will help us with remote troubleshooting. Copyright IBM Corporation,

9 A3.2 Configuration files in the configuration path The configuration path must be created manually, to be pointed to by the environment variable ADA_OPT. Into this path the installer will copy the ADINT/TSM configuration file samples init<sid>,utl and internparamfile.adi from the install package. 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 TSM Client API error log should be placed there as well. A4 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 The responsible administrators should be involved wherever necessary to make sure the data is complete and current. At the end of the preinstall step you should have a verified list of key parameter values, like table 3 on following page, required for the installation and subsequent postinstallation steps. Copyright IBM Corporation,

10 We recommend to enter the actual values into the list below to be used as source during installation as well as documentation of the set-up for later reference. Parameter SAP MaxDB server name sample value use for <dbserv> C2.1 C2.2 required for 1st time inst. required for upgrade inst. X - - required for update inst. SAP MaxDB SID instance name <SID> table 4: # 5 C2.1 X - - SAP MaxDB instance owner name Instance owner password SAP MaxDB administrator name <instance owner> <dbm_user> C2.1 C2.2 admin password <dbm_pwd> C2.1 C2.2 ADINT/TSM usage key not requ. for 60 day trial ADINT/TSM installation directory ADINT/TSM configuration directory TSM client API 64 bit installation directory table 4: # 6 X - - C2.2 X <usage key> C3.3 X X - OS specific, see table 1 OS specific, see table 1 OS specific, see table 1 table 4: # 3 C2.1 table 4: # 4 C2.2 X X X, default - - X X - X, default X X TSM server name <server_a> table 4: #7 X - - TSM node name <maxdb_<sid>> table 4: # 7 X - - TSM node password <node pwd> C3.1 C3.2 TSM mgmt class for full database backup TSM mgmt class for incremental db backup TSM mgmt class for log backup X X - <mgmtclass_a> table 4: # 7 X - - <mgmtclass_b> table 4: # 7 X - - <mgmtclass_c> table 4: # 7 X - - Table 3 List of key parameters for ADINT/TSM set-up Copyright IBM Corporation,

11 B. ADINT/TSM Installation B1 Modes of installation The installer supports 2 special installation modes B1.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.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> B2 Types of installation To preserve as much of existing configuration information as possible you will be asked at the start of the installation which type you want to perform: B2.1 first time installation The installation program will perform a configuration from scratch including a very basic connection to the TSM server. B2.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 new ones. Therefore the ADINT/TSM usage key and the TSM password (if PASSWORDACCESS PROMPT is selected, see A1.5, table 2) will have to be input with the manual commands adint2 -l and adint2 -x <TSM password> during postinstallation. The version count will be restored with the next access to the TSM server. B2.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. Copyright IBM Corporation,

12 B.3 Steps of the ADINT/TSM Installation Program The screens for the interactive installation are listed in below table. Which screens will actually be used is depending on the platform and installation type selected. Nr. Topic 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 Action UNIX/ Windows both both installer will set-up and copy executables both All as set-up by user installer will copy internparamfile.adi installer will copy.init<sid>.utl to configuration path and rename installer will update this user's environment variables ADINT and ADA_OPT with install and config path names installer will update entries in the init<sid>.utl both both UNIX only 1) both 8 preinstallation summary overview of actual parameters both all 9 installation process running both all 10 finish screen both all Table 4 Screen overview for interactive installation Used with Inst. Type All All first time upgrade first time first time first time Notes: 1) for Windows platforms the installer will enter ADINT and ADA_OPT as system variables Copyright IBM Corporation,

13 C. Postinstallation tasks Post installation tasks include completing the configuration in various profiles of ADINT/TSM and TSM defining ADINT/TSM 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 ADA_OPT. 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 ADA_OPT must now be adapted to the desired 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 C 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. The sample profile provided with the install package for a Windows environment is shown on the following page. The sample profile for a UNIX environment only differs in the values for the following 2 parameters: LOGFILE /<path>/<filename> BUFFERSIZE Copyright IBM Corporation,

14 # Sample Profile for ADINT/TSM for Windows, see note below # Range: ('0' means all versions will be kept) MAX_VERSION 3 # Range: ('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: (size (Byte) of the data transfer buffer for ADINT/TSM # and TSM API) BUFFERSIZE # # 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) NCUPDATEMANAGEMENTCLASS <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) # NCUPDATEMANAGEMENTCLASS <mgmtclass_e> # TSM mgmtclass (incr. backup) # LOGMANAGEMENTCLASS <mgmtclass_f> # TSM mgmtclass (log backup) # End of profile Note: If you have defined the TSM management class for incremental backups interactively via the installation program, for example during a first time installation, the following line will be added at the end of the profile UPDATEMANAGEMENTCLASS <mgmtclass_b> You must now manually edit the profile move line UPDATEMANAGEMENTCLASS <mgmtclass_b> after line 'NCUPDATEMANAGEMENTCLASS set the parameter NCUPDATEMANAGEMENTCLASS to the same value as UPDATEMANAGEMENTCLASS. Otherwise the incremental backups will be sent to the TSM default management class. Copyright IBM Corporation,

15 C1.2 TSM profiles Windows C1.2.1 Server Options file ADINT/TSM obtains information for each assigned TSM server from a corresponding options file <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 File dsm.opt The directory designated by DSMI_CONFIG must also contain a file dsm.opt, required by TSM but not used by ADINT/TSM. The example for this file shown below can be copied from the ADINT installation path. Absence of this file will cause an error. ************************************************************************ * Tivoli Distributed Storage Manager * * Sample TSM User Options file DSM.OPT for Windows,ADINT/TSM), see the * * TSM documentation for details. * ************************************************************************ *ErrorLogName c:\maxdb\adint\tsmapierror.log Recommendation: Define the Client API errorlog by a system variable DSMI_LOG rather than in the dsm.opt. Leave the entry in the dsm.opt as a comment. Note: The Tivoli Storage Manager backup/archive client also uses a file dsm.opt (pointed to by variable DSM_CONFIG), which must be kept separate from the Client API dsm.opt (pointed to by variable DSMI_CONFIG). Copyright IBM Corporation,

16 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 Copyright IBM Corporation,

17 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 User 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 ************************************************************************ * Tivoli Distributed Storage Manager * * 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. Copyright IBM Corporation,

18 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 ADINT/TSM via 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). A medium can be defined via CLI, as described below, or via MaxDB GUI. 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 Copyright IBM Corporation,

19 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 by the dbm_user for the database environment. As instance owner issue the following command to log on to the database dbmcli -d <SID> -n <dbserv> -u <dbm_user>,<dbm_pwd> -uutl 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). A medium can be defined via CLI, as described below, or via MaxDB GUI. 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 /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 Copyright IBM Corporation,

20 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, see section A1.5: - 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 D1. 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 and stored in the internparamfile.adi: adint2 -l Starting with release the usage key can also be set via a program using the ADINT command to enable customers with a large number of ADINT copies to change the usage key by program instead of manual input. adint2 -l -k <usage key> Copyright IBM Corporation,

21 D Quick Function Tests D1 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). D2 Validation of the ADINT/TSM to SAP MaxDB connection In order to test backup to TSM a test file can be used instead of a pipe through a manual ADINT/TSM backup command (for UNIX issued as instance owner) adint2 -b -n SAVEDATA1 -p <testfile> where <testfile> is the fully qualified name of a file, e.g. C:\maxdb\adint\init<SID>.utl After the message 'ADINT is waiting for backup commit from MaxDB' type commit and hit 'enter' to close the job. With a query as described in D1 the file will subsequently be shown in the backup repository adint2 -q Copyright IBM Corporation,