ETERNUS SF AdvancedCopy Manager Installation Guide for Tape Backup Option 13.0 -Microsoft(R) Windows(R) 2000/Microsoft(R) Windows Sever(TM) 2003-, -Solaris-, -HP-UX-, -Linux-, -AIX-

Contents Index

Chapter 4 Customization of Tape Server

This chapter explains the customization of the Tape Server of ETERNUS SF AdvancedCopy Manager.

For details of installation in a cluster environment, see the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment" for the operating system of the target Storage Server.

4.1 Flow of Customizing Tape Server

This section explains how to customize the Tape Server.

The procedure is as follows.

1. Installation
2. Customization of Storage Server or Storage Management Server
3. Creation of Access Path Partition
4. Setting up the Port Number
5. Kernel Parameter Tuning
6. Initial Setting of Tape Server
7. TSM Setting (to be done before Setting of Automatic Activation of Daemons)
8. Setting Automatic Activation of Daemons
9. TSM Setting (to be done after Setting of Automatic Activation of Daemons)

4.2 Customization of Storage Server or Storage Management Server

The Tape Server requires customization of the Storage Server. However, when the Tape Server also operates as the Storage Management Server, customization of the Storage Management Server is required. This customization needs to be performed before that of the Tape Server.
For details, see "Customization of Storage Server" or "Customization of Storage Management Server" in the "ETERNUS SF AdvancedCopy Manager Installation Guide (Solaris)".

4.3 Creation of Access Path Partition

To operate the Tape Server, access path partitions are required for each disk array unit.

This section explains how to create the partitions (devices) indicated in "Dynamic Disk Resources".

A file system does not need to be configured in each access path partition.
Four partitions are required for each disk array unit.
Create an access path in a multi-path configuration.

Create each partition so that it can be referenced from the Tape Server. If the Tape Server is a cluster system, set up the partition so that it can be referenced as the same one from each node. For details on creating the partitions, see related Solaris manuals.

4.4 Setting up the Port Number

To operate the Tape Server, port numbers for the ETERNUS SF TSM are required.
For details on indicating the port numbers, see "TSM Setting (to be done before Setting of Automatic Activation of Daemons".

• Setting of a Server Option File
• Setting of a Client System Option File

4.5 Kernel Parameter Tuning

The Tape Server requires tuning of the kernel parameters, which are necessary for operation. This tuning depends on the system type to be set.

To perform the operation indicated in "Customization of Storage Server or Storage Management Server", the values of kernel parameters in that section must be added to the values that are indicated below.

To edit a kernel parameter, add a record for tuning into the /etc/system file or change the current values of the corresponding record.

[Table 4.1 Kernel parameter tuning values]

(*1) The parameters need not be set for Solaris 9 or later version.

(*2) The backup concurrency indicates the number of times backup to tape and restoration from tape are performed during operation. Specify the maximum value for the backup concurrency that is enabled during operation. Normally, a transaction volume has a concurrency of one for one backup command.

An example of editing the /etc/system file is shown below. This is only an example. Use suitable values for your system environment.

set shmsys:shminfo_shmmax = 268435456
set shmsys:shminfo_shmseg = 60
set semsys:seminfo_semmni = 320
set semsys:seminfo_semmns = 670
set semsys:seminfo_semmnu = 542
set semsys:seminfo_semmsl = 35

To register the new kernel parameter values in the system, reboot the system. Use the following command to reboot the system.

# cd /
# /usr/sbin/shutdown -y -i6 -g0

4.6 Initial Setting of Tape Server

This section explains the initial settings that are necessary for operating the Tape Server.

• Required Settings
• Optional Settings

4.6.1 Required Settings

This explains the setting items that are necessary for operating the Tape Server.

4.6.1.1 Setting Access Path Definition Files

Indicate in the /etc/opt/FJSVswstm/conf/devpath.conf file the name of a device that is created in "Creation of Access Path Partition".
The procedure is as follows.

1. Copy the /etc/opt/FJSVswstm/conf/devpath.conf.sample file as /etc/opt/FJSVswstm/conf/devpath.conf.
2. Edit the contents of the /etc/opt/FJSVswstm/conf/devpath.conf file. Indicate one path on one line with "s2" added at the end of the path. An example of editing the /etc/opt/FJSVswstm/conf/devpath.conf file is shown below.

   # devpath.conf # AccessPath for E6000#1 /dev/FJSVmplb/rdsk/mplb2053s2 /dev/FJSVmplb/rdsk/mplb2054s2 /dev/FJSVmplb/rdsk/mplb2055s2 /dev/FJSVmplb/rdsk/mplb2056s2 # AccessPath for E6000#2 /dev/FJSVmplb/rdsk/mplb2057s2 /dev/FJSVmplb/rdsk/mplb2058s2 /dev/FJSVmplb/rdsk/mplb2059s2 /dev/FJSVmplb/rdsk/mplb2060s2

• Indicate four device names for one disk array unit.
• Do not use a path that is used for a volume with a GDS configuration.
• Do not use a path of physical slice that composes VxVM volume.
• A line beginning with # is assumed as a comment line.

4.6.1.2 Setting a TSM Linkage Definition File

Indicate in the /etc/opt/FJSVswstm/conf/tsm.conf file the information for connecting to a server and a client of the ETERNUS SF TSM.
The procedure is as follows.

1. Copy the /etc/opt/FJSVswstm/conf/tsm.conf.sample file as /etc/opt/FJSVswstm/conf/tsm.conf.
2. Change the file owner and file mode of the /etc/opt/FJSVswstm/conf/tsm.conf file. Set the file so that it can be accessed only from a super-user (owner is root, file mode is 0600). An example of changing and checking the file owner and file mode is shown below.

   # cd /etc/opt/FJSVswstm/conf # chown root tsm.conf # chmod 600 tsm.conf # ls -l tsm.conf -rw------- 1 root other 66 May 21 17:17 tsm.conf #

3. Edit the contents of the /etc/opt/FJSVswstm/conf/tsm.conf file. An example of editing the /etc/opt/FJSVswstm/conf/tsm.conf file is shown below.

   SERVER_USERID="admin" SERVER_PASSWD="admin" CLIENT_PASSWD="admin"

   The meaning of each item is as follows.

   Item	Meaning
   SERVER_USERID	Defines a user ID for connecting to a TSM server, enclosed in "", following "=". This user ID defines the same administrator ID as one that is specified to register (register admin) a TSM administrative client.
   SERVER_PASSWD	Defines the password for a user ID for connecting to a TSM server, enclosed in "", following "=". This password defines the same administrator password as one that is specified to register (register admin) a TSM administrative client.
   CLIENT_PASSWD	Defines the password for a server name (SERVERname) that is indicated in a TSM client system option file (dsm.sys), enclosed in "", following "=". This password defines the same password as one that is specified to register (register node) a TSM client.

A line beginning with # is assumed as a comment line.

4.6.1.3 Checking Definition Files

This explains how to check an access path definition file (devpath.conf) and a TSM linkage definition file (tsm.conf).
The procedure is indicated below.

1. Execute a Tape Server definition file check command (tbochkconf).

   # /opt/FJSVswstm/bin/tbochkconf tbochkconf completed #

If an error occurs, a message indicating the corresponding file name and line number is displayed. Correct the location with the error and execute the tbochkconf command again.
For details of the tbochkconf command, see "Tape Server definition file check command (tbochkconf)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option".

4.6.1.4 Collection the Information of ETERNUS3000 Disk Array Unit

When the RAID device connected to the Tape Server is an ETERNUS3000 disk array unit, the disk configuration information must be collected.

This operation does not need to be performed when the RAID device connected to the Tape Server is an ETERNUS6000, ETERNUS4000, ETERNUS8000, or GR series unit.

The procedure is indicated below.

+When GR720 and GR730 are not used together

1. Execute an information collection command for ETERNUS3000 disk array unit.

   # /opt/FJSVswstm/bin/tbogetoluinfo -l IP_address tbogetoluinfo completed #

   Specify an IP address of ETERNUS3000 disk array unit for IP_address in IPv4 format. An example of the execution is shown below.

   # /opt/FJSVswstm/bin/tbogetoluinfo -l 10.124.6.10 tbogetoluinfo completed #

2. Have the GR multi-path driver read the information.

   # mplbconfig -q #

+When GR720 and GR730 are used together

When the RAID device connected to the Tape Server includes a GR720, GR730, and ETERNUS3000 disk array unit, the information collection command (tbogetoluinfo) and the mplbconfig -q function cannot be used. In this case, perform the following procedure.

1. Login to ETERNUSmgr of ETERNUS3000 disk array unit.
2. Click [Setting RAID/Setting Host] from the Main menu.
3. Click [Change assigned CM for RAID Group] from the [Setting RAID/Setting Host] menu.
4. Select the checkbox of [A dynamic change of CM for RAID Group is not performed.] for "CM dynamic change set up for RAID Group".
5. Click the [Set] button.

4.6.1.5 Creation of a TSM Environment File to Backup

Create a TSM environment file that is required to backup the tape management information.
The procedure is indicated below.

1. Copy the /etc/opt/FJSVswstm/conf/tsmbkfile.sample file as /etc/opt/FJSVswstm/conf/tsmbkfile.
2. As required, edit the contents of the /etc/opt/FJSVswstm/conf/tsmbkfile file. If "$DIR4" (a database directory of the ETERNUS SF TSM) whose amount of disk space is estimated in "Disk Space Requirement" differs from that of the TSM standard directory, edit the contents of tsmbkfile (the standard directory is /opt/tivoli/tsm/server/bin).
   For details of the contents to be edited, see "Backup of tape management information" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option".

For details of the backup of the tape management information, see "Tape management information backup command (tboresback)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option".

4.6.2 Optional Settings

Valid optional settings are not currently available.

4.7 TSM Setting (to be done before Setting of Automatic Activation of Daemons)

This section explains the TSM setting to be done before the setting of automatic activation of daemons.

Locate the following file and database in "$DIR4" (a database directory of the ETERNUS SF TSM) whose amount of space is estimated in "Disk Space Requirement".

• Server option file
• Database and log file

This database directory of the ETERNUS SF TSM is hereinafter called a "DB directory". Normally, specify /opt/tivoli/tsm/server/bin.

4.7.1 Driver Setting of Tape Library System

This explains the driver setting of the tape library system that the TSM system of the Tape Server uses. The procedure is indicated below.

1. Set up the robot.
2. Set up the IBM Tape Driver.
3. Set up the FC-SW connection. (For the FC-SW connection only)
4. Set up the FC direction connection. (For the FC direct connection only)

The definition depends on the type of the tape library system. For details, see the "ETERNUS SF TSM ETERNUS LT Library Operation Guide (LT160)".

4.7.2 Setting of a Server Option File

This explains how to write the definitions related to a TSM server operation to the dsmserv.opt file. The dsmserv.opt file is stored in "$DIR4" ("DB directory") whose amount of space is estimated in "Disk Space Requirement".
The procedure is as follows.

1. Copy /opt/tivoli/tsm/server/bin/dsmserv.opt (that is sample file) to "DB directory". In the following example, "DB directory" is described as DB_directory. When the dsmserv.opt file is located in /opt/tivoli/tsm/server/bin, this operation is not required

   # cp /opt/tivoli/tsm/server/bin/dsmserv.opt DB_directory

2. Edit the contents of the dsmserv.opt file under the "DB directory". An example of editing the contents of the dsmserv.opt file is shown below.

   VOLUMEHistory /opt/tivoli/tsm/server/bin/volhist.out DEVCONFig /opt/tivoli/tsm/server/bin/devconfig.out EXPInterval 1 COMMmethod SHAREDMEM SHMPort 1510

   The meaning of each item is as follows.

   Item	Meaning
   VOLUMEHistory	Specifies in a full path the name of a file to which to save the copy of sequential-volume information. For the directory, specify "DB directory". The file name is volhist.out. Normally specify "/opt/tivoli/tsm/server/bin/volhist.out".
   DEVCONFig	Specifies in a full path a file to which to save the copy of device configuration information. For the directory, specify "DB directory". The file name is devconfig.out. Normally specify "/opt/tivoli/tsm/server/bin/devconfig.out".
   EXPInterval	Specifies an interval (days) between automatic checks for files whose validity has expired. Beginning at the startup point of the TSM daemon, checks for term expirations are made using the specified interval (days). Normally specify 1.
   COMMmethod	Specifies a communication protocol. Indicate the following value. SHAREDMEM
   SHMPort	Specifies the TCP/IP port number of shared memory. Indicate the following value. 1510 When the system is using 1510, specify a free port number from 1000 to 32767.
   MAXSessions	Specifies the simultaneous number of sessions of a TSM client that can connect to a TSM server. Specify the following value. Tape backup concurrency x 2 (*1) If the calculated value is 25 or less, specify 25. This is the TSM default value. (*1) The backup concurrency indicates the number of times backup to tape and restoration from tape are actually performed. Specify the maximum value of the backup concurrency that is enabled during operation. Normally, a transaction volume has a concurrency of one for one backup command.

A line beginning with * is assumed as a comment line.
Be careful not to use in another software product the port numbers that are specified for SHMPort and HTTPport.
For details on setting the server option file, see the "ETERNUS SF TSM Administrator's Guide" and the "ETERNUS SF TSM Administrator's Reference".

4.7.3 Setting of a Client System Option File

This explains how to write the definitions related to a TSM client operation to the /usr/bin/dsm.sys and /usr/bin/dsm.opt files.
The procedure is as follows.

1. Edit the contents of the /usr/bin/dsm.sys file. An example of editing the /usr/bin/dsm.sys file is shown below. Items after nodename must begin with a space (or tab).

   SERVERname tapeserver1 nodename tapeserver1 COMMmethod SHAREDMEM SHMPort 1510 PasswordAccess generate

   The meaning of each item is as follows.

   Item	Meaning
   SERVERname	Specifies a node name of Tape Server.
   Nodename	Specifies a node name of Tape Server.
   COMMmethod	Specifies a communication protocol. Indicate the following value. SHAREDMEM
   SHMPort	Specifies a shared memory TCP/IP port number. Indicate the following value. 1510 When the system is using 1510, specify a free port number from 1000 to 32767 (specify the same value as that specified in dsmserv.opt).
   PasswordAccess	Specifies how to update the password that a TSM client uses. Indicate the following value. generate

   

   A line beginning with * is assumed as a comment line.
   Be careful not to use in another software product the port number that is specified for SHMPort.

2. Edit the contents of the/usr/bin/dsm.opt file. An example of editing the /usr/bin/dsm.opt file is shown below.

   SERVERname tapeserver1

   The meaning of each item is as follows.

   Item	Meaning
   SERVERname	Specifies a node name of Tape Server.

   

   A line beginning with * is assumed as a comment line.
   For details on setting the client system option file, see the "ETERNUS SF TSM Administrator's Guide" and the "ETERNUS SF TSM Administrator's Reference".

4.7.4 Formatting a Database and Log File

This explains how to format a database and log file. The database and log file are stored in "$DIR4" ("DB directory") whose amount of space is estimated in "Disk Space Requirement".

The functions for extending the TSM database and log file (extend db and extend log) cannot be used. Specify a value large enough to change the backup operation in the future.
For details on extending the space of the ISM database and log file, see the "ETERNUS SF TSM Administrator's Guide" and the "ETERNUS SF TSM Administrator's Reference".

The procedure is as follows.

1. Set up the shell and environment variables that are required in the following operations. The following is an example of /bin/sh or /bin/ksh command execution in prompt.

   # TSMDB=DB_directory # DSMSERV_DIR=/opt/tivoli/tsm/server/bin; export DSMSERV_DIR # DSMSERV_CONFIG=$TSMDB/dsmserv.opt; export DSMSERV_CONFIG #

2. Delete the database and log file that are created through installation.

   # cat /opt/Tivoli/tsm/server/bin/dsmserv.dsk #dsk_comment#page_shadow_token:1050524192947 /opt/tivoli/tsm/server/bin/log.dsm /opt/tivoli/tsm/server/bin/db.dsm # rm /opt/tivoli/tsm/server/bin/log.dsm # rm /opt/tivoli/tsm/server/bin/db.dsm # rm /opt/tivoli/tsm/server/bin/dsmserv.dsk #

   Refer the file that contains the database and log file, and find the log.dsm and db.dsm file paths.
   Next, delete the log.dsm and db.dsm files and then delete the file that contains the database and log file.

3. Create the database and log file and format them.

   # cd $TSMDB # /opt/tivoli/tsm/server/bin/dsmfmt -m -db database_file_name database_file_size # /opt/tivoli/tsm/server/bin/dsmfmt -m -log log_file_name log_file_size #

   The meaning of the specified items is as follows.

   Item	Meaning
   database_file_name	Specifies in a full path the file name of a database to be created. For the directory, specify "DB directory". The file name is db.dsm. Normally specify "/opt/tivoli/tsm/server/bin/db.dsm".
   log_file_name	Specifies in a full path the file name of a log to be created. For the directory where the file is created, specify "DB directory". The file name is log.dsm. Normally specify "/opt/tivoli/tsm/server/bin/log.dsm".
   database_file_size	Specifies the size of a database to be created (in megabytes). Specify the value that is estimated in "Dynamic Disk Resources". Specify a value large enough to change the backup operation in the future.
   log_file_size	Specifies the size of a log file to be created. Specify the following or larger value (in megabytes). Specify a value large enough to change the backup operation in the future. 128

   An example of the execution is shown below.

   # cd $TSMDB # /opt/tivoli/tsm/server/bin/dsmfmt -m -db $TSMDB/db.dsm 129 # /opt/tivoli/tsm/server/bin/dsmfmt -m -log $TSMDB/log.dsm 128 #

4. Format the database and log file.

   # cd $TSMDB # /opt/tivoli/tsm/server/bin/dsmserv format 1 $TSMDB/log.dsm 1 $TSMDB/db.dsm #

   For log.dsm and db.dsm, specify the file names that are specified with the dsmfmt command.

For details on formatting the database and log, see the "ETERNUS SF TSM Administrator's Guide" and the "ETERNUS SF TSM Administrator's Reference".

4.7.5 Registration of a TSM Administrative Client and TSM Server Name

This explains how to register a TSM client and TSM server name. Use the shell and environment variables that are used in "Formatting a Database and Log File".
The procedure is as follows.

1. Activate the TSM server daemon manually. If the activation succeeds, a prompt with "TSM>" is displayed.

   

   To make the setting here, the TSM server daemon must be activated manually. If the daemon is automatically activated, the setting is disabled.

   # cd $TSMDB # /opt/tivoli/tsm/server/bin/dsmserv : : TSM>

2. Register the TSM administrator ID and password.

   TSM> register admin ID password passexp=expire_prior

   For the ID and password, use the values that are set in "Setting a TSM Linkage Definition File". For the expire_prior that is the password validity term, specify 0 (infinite). An example of the execution is shown below.

   TSM> register admin admin admin passexp=0

3. Authorize the administrator.

   TSM> grant authority ID class=system

   For the ID, specify the administrator ID that is set above. An example of the execution is shown below.

   TSM> grant authority admin class=system

4. Set the TSM server name.

   TSM> set servername server_name

   For the server_name, specify SERVERname that is set in the client system option file (dsm.sys). An example of the execution is shown below.

   TSM> set servername tapeserver1

5. Deactivate the TSM server daemon.

   TSM> halt

   

   Execute the halt command in the prompt where the TSM server daemon is activated (not the shell command prompt).

For details on registering the TSM administrative client and TSM server name, see the "ETERNUS SF TSM Administrator's Guide" and the "ETERNUS SF TSM Administrator's Reference".

4.8 Setting Automatic Activation of Daemons

The Tape Server has the following daemons.

• Daemon as Storage Server or Storage Management Server
• Tape Server Daemon
• TSM Server Daemon

The following explains the setting for automatically activating daemons.

4.8.1 Daemon as a Storage Server or Storage Management Server

For details of the daemon as a Storage Server or Storage Management Server, see "Automatic Activation of Daemons" in the "ETERNUS SF AdvancedCopy Manager Installation Guide (Solaris)".

4.8.2 Tape Server Daemon

To automatically activate the Tape Server daemon, see "Initial Setting of Tape Server".

Even if the system is started up, the Tape Server daemon cannot be activated until "Initial Setting of Tape Server" is completed. In this case, complete "Initial Setting of Tape Server" and then reboot the system.
To activate or deactivate the Tape Server daemon alone, see "Activation and Deactivation of a daemon" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option".

4.8.3 TSM Server Daemon

To automatically activate the TSM server daemon, make the following settings.

1. Copy /opt/tivoli/tsm/server/bin/initTSM to /etc/init.d/initTSM.

   # cp /opt/tivoli/tsm/server/bin/initTSM /etc/init.d/initTSM #

   
   
2. Change the file owner and file mode of the /etc/init.d/initTSM file. Set the file so that it can be accessed from the super-user only, and select an execution-enabled mode (owner is root, file mode is 0700). An example of changing and checking the file owner and file mode is shown below.

   # cd /etc/init.d # chown root initTSM # chmod 700 initTSM # ls -l initTSM -rwx------ 1 root other 1228 May 26 17:05 initTSM #

3. To start up or shut down the system, create the following symbolic link files.

   /etc/rc2.d/S99tsmsv	is TSM server daemon activation script
   /etc/rc0.d/K00tsmsv	is TSM server daemon deactivation script

   An example of the execution is shown below.

   # ln -s /etc/init.d/initTSM /etc/rc2.d/S99tsmsv # ln -s /etc/init.d/initTSM /etc/rc0.d/K00tsmsv #

4. Edit the contents of the /etc/init.d/initTSM file. An example of editing the contents of the /etc/init.d/initTSM file is shown below.

   : : 'start') TSMDB=/opt/tivoli/tsm/server/bin : : 'stop') ID=admin PA=admin : :

   The meaning of the specified item is as follows.

   Item	Meaning
   TSMDB	Defines the storage path name of a TSM server database following "=". For the path name, specify a "DB directory".
   ID	Defines the user ID to connect to a TSM server, following "=". This user ID defines the same administrator ID as one that is specified to register a TSM administrative client (register admin).
   PA	Defines the password for the user ID to connect to a TSM server, following "=". This password defines the same administrator password as one that is specified to register a TSM administrative client (register admin).

4.9 TSM Setting (to be done after Setting of Automatic Activation of Daemons)

This section explains how to make the TSM settings to be done after the automatic activation of daemons is completed.

When the setting to automatically activate daemons is completed, reboot the system and activate all the daemons on the Tape Server.

Before performing all of the following operations, execute a TSM administrative client command (dsmadmc). If the prompt with "tsm>" is displayed in the example of the execution, execute the TSM administrative client command (dsmadmc) and then perform the operations.

The following indicates how to start and stop the TSM administrative client command and TSM client command.

+How to start TSM administrative client command

1. Execute the TSM administrative client command (dsmadmc). After the execution, the "tsm>" prompt is displayed. An example of the execution is shown below.

   # cd /opt/tivoli/tsm/client/ba/bin # ./dsmadmc IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 3.0 (c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved. Enter your user id: admin Enter your password: Session established with server ********: Solaris 8/9 : : tsm>

   For [Enter your user id], enter the TSM administrator ID and press the Return key. For [Enter your password], enter the TSM administrator password and press the Return key.

+How to Stop TSM administrative client command

1. To stop the TSM administrative client command (dsmadmc), enter "quit" in the "tsm>" prompt. An example of the execution is shown below.

   : : tsm> quit

4.9.1 Registration of License Password

This explains how to register the license password in the TSM system.
The procedure is as follows.

1. Register the license password.

   tsm> register license file=license_file_name number=number_of_license

2. Check the registered license information.

   tsm> query license

For details of the license registration, see "Managing Server Operations" in the "ETERNUS SF TSM Administrator's Guide".
The required license depends on whether a library is shared between the Tape servers. For details of the license, see the "ETERNUS SF TSM Administrator's Guide".

4.9.2 Registration of Client Node

This explains how to register the client node in the TSM system.
The procedure is as follows.

1. Register the TSM administrator ID and password.

   tsm> register node client_ID password passexp=expire_prior maxnummp=maxnum_mntpnt

   For the client_ID, specify a tape server node name. For the password, use the value that is set in "Setting a TSM Linkage Definition File". For the expire_prior, specify 0 (infinite). For the maxnum_mntpnt, specify 999 (maximum value). An example of the execution is shown below.

   tsm> register node tapeserver1 admin passexp=0 maxnummp=999

2. Confirm the client node information.

   tsm> query node format=detail

For details of the client node registration, see the "ETERNUS SF TSM Administrator's Guide".

4.9.3 Setting a TSM Environment

This explains how to make the TSM environment related settings.
The procedure is as follows.

1. Define the preservation days of an activity log.

   tsm> set actlogretention days

   An example of the execution is shown below.

   tsm> set actlogretention 100

For details of the TSM environment related settings, see the "ETERNUS SF TSM Administrator's Guide".

4.9.4 Setting a Tape Library System

This explains how to set up the tape library system in the TSM system.

4.9.4.1 When a Tape Library System is not shared between Tape Servers

The setting procedure applied when the tape library system is not shared between the Tape Servers (for example, there is only one Tape Server) is as follows.

1. Set the tape library (controller) system. (define library)
2. Set the tape library path. (define path)
3. Set the drive. (define drive)
4. Set the drive path. (define path)
5. Execute steps 1 to 4 on each Tape Server.

The definitions depend on the type of the tape library system. For details, see the "ETERNUS SF TSM ETERNUS LT Library Operation Guide (LT160)".

4.9.4.2 When a Tape Library System is shared between Tape Servers

The setting procedure applied when the tape library is shared between the Tape servers is as follows.

+Setting on library management server

1. Set the shared tape library (controller) system. (define library)
2. Set the tape library path for the library management server. (define path)
3. Set the drive. (define drive)
4. Define the drive path. (define path)

+Setting on library client server

1. Set the shared tape library (controller) system. (define library)

+Setting on library management server

1. Set the tape library path for the library client server. (define path)

The definitions depend on the type of the tape library system. For details, see the "ETERNUS SF TSM ETERNUS LT Library Operation Guide".

Contents Index