Top
ETERNUS SF AdvancedCopy Manager 14.2 Installation and Setup Guide

8.6.1 Required Configurations

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

8.6.1.1 Configuration of Access Path Definition Files

Indicate in the /etc/opt/FJSVswstm/conf/devpath.conf file the name of a device that is created in "8.3 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

    Note

    • Specify four device names for each 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 to be a comment line only.

    • If an ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000 or ETERNUS4000 is used, select two access paths from the multi-paths managed by each CM of the ETERNUS disk storage systems.

8.6.1.2 Configuration of 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.

    Note

    A line beginning with # is assumed to be a comment line.

8.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.

Execute tbochkconf (Tape Server definition file check command).

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

Note

If an error occurs, a message indicating the corresponding file name and line number is displayed. Correct the error at that location and execute the tbochkconf command again.

For details of the tbochkconf command, see "tbochkconf (Tape Server definition file check command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option".

8.6.1.4 Collecting ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, and ETERNUS4000 information

When the RAID device connected to the Tape Server is an ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, or ETERNUS4000, the disk configuration information must be obtained.

Note

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

The procedure is indicated below.

When GR720 and GR730 are not used together

  1. Execute tbogetoluinfo (ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 information acquisition command) for the ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000.

    # /opt/FJSVswstm/bin/tbogetoluinfo -l ETERNUS IP_address
    ETERNUS I
    P_address completed. [total olu = VALUE] /var/opt/FJSVmplb/mplb_ext.conf was update. Or The configuration file of CM information was update. #

    Specify an IP address of an ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 for <ETERNUS IP_address> in IPv4 format. An example is provided below.

    # /opt/FJSVswstm/bin/tbogetoluinfo -l 10.124.6.10
    10.124.6.10 completed. [total olu = 100]
    The configuration file of CM information was update.
    #
  2. Have the GR multipath driver read the LUN information. This procedure is not required if an ETERNUS multipath driver is installed in the Tape Server.

    # mplbconfig -q
    #

    Note

    Do not execute this command while the RAID migration process is in progress.

When GR720 and GR730 are used together

When the RAID device connected to the Tape Server includes ETERNUS GR720/GR730 and ETERNUS3000, tbogetoluinfo (ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 information acquisition command) and the mplbconfig -q function cannot be used. In this case, perform the following procedure.

8.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 "7.3.2 Dynamic Disk Resources" 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".

See

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