Tivoli Header

Quick Start


Setup Procedure

The following is an overview of the steps required to set up a Tivoli Storage Manager server in an HACMP cluster:

  1. Install and Configure HACMP for AIX.
  2. Install the Tivoli Storage Manager Server on the Production Node.
  3. Install the Tivoli Storage Manager Client on the Production Node.
  4. Configure the Tivoli Storage Manager Server.
  5. Set Up the Standby Node. Install and configure the Tivoli Storage Manager server and client on the standby node.
  6. Define the Removable Media Storage Devices to AIX. On the production and standby nodes, define to AIX the removable media storage devices that Tivoli Storage Manager will use.
  7. Complete the HACMP and Tivoli Storage Manager Configurations. Define the Tivoli Storage Manager server as an application owned by the production node and a failover resource of the standby node. Complete the Tivoli Storage Manager server configuration.

Install and Configure HACMP for AIX

  1. Define the shared disk space (volume groups) that will hold the Tivoli Storage Manager server database, recovery log, and storage pools you plan to use. This procedure assumes that the dsmserv.opt and dsmserv.dsk files will be put in a shared file system called /tsm, along with the following files: checkdev, opendev, scsireset, scsitest, verdev, startserver, and stopserver.

    You do not have to use the same name for your shared file system. The examples in this section and in the sample scripts are set up to use this as the shared file system. If you use another name for the file system, you must make the modifications in the scripts that are described here.

  2. Define the shared file system and other shared file systems and logical volumes, as required. You may want to put files in separate file systems or on separate physical disks for integrity or performance reasons. To provide maximum availability, logical volumes (including those underlying file systems) should be mirrored.
  3. Configure HACMP so that the production node owns the shared volume groups and the standby node takes over the shared volume groups if the production node fails.
  4. Configure HACMP so the file systems also fail over.
  5. Configure HACMP so the standby node takes over the production node's IP address in the event of failure.
  6. Mount /tsm on the production node.

Configuring the removable media storage devices for failover and defining the Tivoli Storage Manager server as an application to HACMP is described in a later step.

Install the Tivoli Storage Manager Server on the Production Node

Perform the following steps:

  1. Install the Tivoli Storage Manager server. See Installing Tivoli Storage Manager. At a minimum the following filesets are required:

    For AIX 4.3.3

    tivoli.tsm.server.com

    tivoli.tsm.server.rte

    tivoli.tsm.msg.[lang].server

    tivoli.tsm.devices.aix43.rte

    tivoli.tsm.msg.[lang].devices

    tivoli.tsm.license.rte

    tivoli.tsm.license.cert

    For AIX 5.1 (32bit)

    tivoli.tsm.devices.aix5.rte

    For AIX 5.1 (64bit)

    tivoli.tsm.server.aix5.rte64

    tivoli.tsm.license.aix5.rte64

    tivoli.tsm.devices.aix5.rte

    Note:
    For AIX 5.1 installation, replace the filesets in AIX 4.3.3 with the corresponding filesets in AIX 5.1, and install all other filesets from AIX 4.3.3
    The executable files will typically be installed on the internal disks of the production node, not on the shared Tivoli Storage Manager disk space. Tivoli Storage Manager server executable files will install in the /usr/tivoli/tsm/server/bin directory.
  2. Configure Tivoli Storage Manager to use the TCP/IP communication method. See Chapter 3, Specifying Server and Client Communication Methods. TCP/IP is the default in dsmserv.opt.smp. Create a directory called /tsm/files and copy dsmserv.opt.smp to /tsm/files/dsmserv.opt.

    Although not required, we recommend that you put a line in /etc/services on both hosts defining port 1500. This indicates that it cannot be used by other applications.

  3. For information about running the server from a directory different from the default database that was created during the server installation, see Running Multiple Servers on a Single Machine.
    1. Issue the following commands:
      cd /tsm/files
      export DSMSERV_CONFIG=./dsmserv.opt
      export DSMSERV_DIR=/usr/tivoli/tsm/server/bin 
      
    2. Allocate the Tivoli Storage Manager database, recovery log, and storage pools on the shared Tivoli Storage Manager volume group.
    3. Issue the dsmfmt command to format files residing in file systems.
    4. Issue the dsmserv runfile command to load the database for using the administrative Web interface, if needed.
    5. Issue the dsmserv format command to install the database which will create the dsmserv.dsk file in the current directory.
  4. Copy files from the server directory into a directory in the shared file system, by issuing the following commands:
    mkdir /tsm/bin 
    cp /usr/tivoli/tsm/server/bin/verdev /tsm/bin/verdev 
    cp /usr/tivoli/tsm/server/bin/checkdev /tsm/bin/checkdev 
    cp /usr/tivoli/tsm/server/bin/opendev /tsm/bin/opendev 
    cp /usr/tivoli/tsm/server/bin/scsireset /tsm/bin/scsireset 
    cp /usr/tivoli/tsm/server/bin/scsitest /tsm/bin/scsitest 
    cp /usr/tivoli/tsm/server/bin/startserver /tsm/bin/startserver 
    cp /usr/tivoli/tsm/server/bin/stopserver /tsm/bin/stopserver 
    
  5. Clean up the default server installation. These steps are not required.
    1. You can use rmitab autosrvr to remove the entry from /etc/inittab that starts the Tivoli Storage Manager server. If this step is not performed, make sure that this server and the server running from the /tsm/files directory are configured to use different TCP/IP ports.
    2. Remove the default created database, recovery log, and dsmserv.dsk file from the /usr/tivoli/tsm/server/bin directory. This will save a little space in the /usr directory if these files are not needed

Install the Tivoli Storage Manager Client on the Production Node

Install the client on the production node. Detailed instructions are in Backup-Archive Installation and User's Guide.

  1. Install the Tivoli Storage Manager client executable files. The fileset name is tivoli.tsm.client.ba.aix43.32bit. These files will typically be installed on the internal disks of the production node, not on the shared Tivoli Storage Manager disk space. Tivoli Storage Manager client executable files will install in the /usr/tivoli/tsm/client/ba/bin directory.
    Note:
    You only need to install the administrative client. The fileset contains the backup-archive client files (command line and GUI) and the administrative client (command line). The backup-archive client is not supported with HACMP and should not be used on the production or standby nodes because it does not contain failover support. The administrative client command line is required because it is called by the stopserver script to halt the Tivoli Storage Manager server in a fallback situation.
  2. Set up the dsm.sys client options file used by the Tivoli Storage Manager client to find the server. The server name does not have to be the same name specified on the SET SERVERNAME command when activating the server (see step 3 in Configure the Tivoli Storage Manager Server). The server name in dsm.sys is used only on the -servername parameter of the dsm, dsmc, and dsmadmc commands to specify the server to be contacted.

Configure the Tivoli Storage Manager Server

Do the following to configure the Tivoli Storage Manager server:

  1. Start the Server

    Issue the following commands:

    cd /tsm/files 
    export DSMSERV_CONFIG=./dsmserv.opt 
    export DSMSERV_DIR=/usr/tivoli/tsm/server/bin
    
    Then start the server using the dsmserv command with no parameters.
  2. Issue the REGISTER LICENSE command to register the required licenses. Follow the instructions in Registering Licenses.
  3. Use the SET SERVERNAME command to name the Tivoli Storage Manager server.
  4. Use the QUERY DBVOLUME and QUERY LOGVOLUME commands to verify that all the database and recovery log volumes are on the shared disk only.
  5. Prepare storage pools for backup and archive files:
    1. Use the DEFINE VOLUME command to add disk storage pool volumes created on the shared disk to the disk storage pools.
    2. Use the QUERY VOLUME command to verify that the only disk storage pool volumes that are defined all reside on the shared disk
  6. Register an administrator that HACMP will use to control the Tivoli Storage Manager server, and grant the administrator storage and operator privilege.
  7. Edit the /tsm/bin/stopserver shell script and update the user ID and password in it to the values set in step 6. Update the server name in the script to the dsm.sys stanza label set in step 2.

Set Up the Standby Node

Ensure that the Tivoli Storage Manager server is not running on the production node.

  1. On the standby node, bring up the shared volume group and any Tivoli Storage Manager file systems (including /tsm).
  2. On the standby node install the Tivoli Storage Manager as was described in Install the Tivoli Storage Manager Server on the Production Node. If the executable files are installed on shared disk space, you may need to install them on the standby node because Tivoli Storage Manager device drivers, smit panels, and other files must be installed in AIX system directories.
  3. You can optionally perform the clean-up of the default server installation on the standby node as described in Install the Tivoli Storage Manager Server on the Production Node.
  4. Start the server on the standby node as described in step 1 in Configure the Tivoli Storage Manager Server. Query the database, recovery log, and storage pool volumes to verify that they are the same as when the server was started on the production node.
  5. Install the client on the standby node as described in Install the Tivoli Storage Manager Client on the Production Node. If the executable files are installed on shared disk space, you may need to install them on the standby node because Tivoli Storage Manager smit panels, and other files must be installed in AIX system directories. Use the AIX rcp command with the -p flag to copy the dsm.sys file from the production node to the standby node. If the dsm.sys file is changed on one node, it must be copied to the other node.
Note:
If the dsm.sys file is changed on one node, you must copy it to the other node.

Define the Removable Media Storage Devices to AIX

On the production and standby nodes, define to AIX the removable media storage devices that will be used by Tivoli Storage Manager. Follow the instructions in Using Tape Devices and Optical Devices

Edit the /tsm/bin/startserver shell script and change the VerifyDevice commands in the shell script to specify the removable media storage devices that will be used by Tivoli Storage Manager. Change the cd command near the end of the shell script to cd /tsm/files.

Note:
A VerifyDevice command is not needed to fail over an IBM 3494 Library Manager. The Library Manager is not connected via SCSI, so no special logic is required to fail it over.

Ensure that the removable media storage devices are configured with the same names on the production and standby nodes. You may have to define "dummy" devices on one of the nodes to accomplish this. To define a "dummy" device, do the following:

  1. Issue the command 'smit devices' and go through the smit panels to define the device.
  2. Choose an unused SCSI address for the device.
  3. Instead of pressing Enter on the last panel to define the device, press F6 instead to obtain the command smit is about to execute.
  4. Exit from smit and enter the same command on the command line, adding the -d flag to the command. If you attempt to define the device using smit, the attempt will fail because there is no device at the unused SCSI address you have chosen.

Complete the HACMP and Tivoli Storage Manager Configurations

Update the HACMP configuration to define the Tivoli Storage Manager server as an application, owned by the production node and a failover resource of the standby node. HACMP can invoke the startserver and stopserver shell scripts to start and stop the Tivoli Storage Manager server.

Note:
The startserver shell script takes care of breaking any SCSI RESERVE on the removable media storage devices.
Continue with configuring the Tivoli Storage Manager server.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]