Configuring IBM Storage Protect server on a secondary node for PowerHA with a shared Db2 instance

Edit online

If the IBM Db2 instance directory is shared between the nodes in the PowerHA® cluster, you do not have to create a Db2 instance on the secondary node. You do not run the dsmicfgx wizard.

Procedure

To configure a server instance on the secondary node with a shared Db2 instance, complete the following steps:

  1. On each node in the cluster, add the following text to the /opt/tivoli/tsm/server/bin/rc.dsmserv script: 
    DB2NODES_TEMP='/tmp/db2nodes.tmp'
DB2NODES=${homeDir}/sqllib/db2nodes.cfg
# Current hostname
HOSTNAME=$(/bin/hostname)
# hostname saved in db2nodes.cfg
DB2_HOST=$(cat $DB2NODES | cut -d ' ' -f 2)
# if they are different update the file
if [[ "$HOSTNAME" != "$DB2_HOST" ]]
then
  echo "Updating hostname in db2nodes.cfg"
  sed -e s_${DB2_HOST}_${HOSTNAME}_g $DB2NODES > $DB2NODES_TEMP
  cp $DB2NODES_TEMP $DB2NODES
fi
    Tip: If the text is not included in the script, you can include it before you issue /opt/tivoli/tsm/server/bin/rc.dsmserv script.
  2. Move all the shared resources to the secondary node.
  3. Update the following variables in the /opt/tivoli/tsm/server/bin/startserver script, by using the following values:
    Table 1. Variables in the /opt/tivoli/tsm/server/bin/startserver script
    Description Variable Example
    Set the INST_USER to the instance user ID. INST_USER INST_USER='tsmuser1'
    Set the INST_DIR to the location of the IBM Storage Protect instance directory. This directory contains dsmserv.dbid and dsmserv.opt. INST_DIR INST_DIR='/home/tsmuser1/tsminst1'
    Select one of the following startup options:

    Option 1 - use instance:

    $INST_USER but run the server as root (-U)

    Option 2 - use instance:

    $INST_USER and run the server as $INST_USER (-u)

    		 INST_OPTION

    Option 1:

    INST_OPTION='-U $INST_USER'

    Option 2:

    INST_OPTION='-u $INST_USER'
  4. Update the /etc/services file by adding the following entry: 
          DB2_<instance>     60000/tcp
      DB2_<instance>_1   60001/tcp
      DB2_<instance>_2   60002/tcp
      DB2_<instance>_3   60003/tcp
      DB2_<instance>_4   60004/tcp
      DB2_<instance>_END 60005/tcp
      db2c_<instance>   <connection port>/tcp
    Tip: By default, port 50000 is reserved for client to server connection requests, and the first available four ports after 60000 are reserved for IBM Storage Protect Snapshot communication.
    Example:
          DB2_tsminst1     60000/tcp
      DB2_tsminst1_1   60001/tcp
      DB2_tsminst1_2   60002/tcp
      DB2_tsminst1_3   60003/tcp
      DB2_tsminst1_4   60004/tcp
      DB2_tsminst1_END 60005/tcp
      db2c_tsminst1    50000/tcp
  5. Start the server by issuing the following script: 
    /opt/tivoli/tsm/server/bin/startserver
    Tip: If the IBM Storage Protect server instance fails to start, the following error might be displayed:
    DBI1306N The instance profile is not defined
    To prevent this error from occurring, ensure that you are starting the server by using the /opt/tivoli/tsm/server/bin/startserver script.
  6. When the server is started, issue the BACKUP DB command to verify that the data is successfully backed up.
  7. Install the client on the standby node. If the executable files are installed on shared disk space, you might need to install them on the standby node. IBM Storage Protect SMIT panels and other files must be installed in AIX® system directories. Use the AIX RCP command with the -p option 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.