Chapter 18. VERITAS Cluster Server on AIX and IBM Tivoli Storage Manager Server 753
7. After the installation has been successfully completed, we review the installed
filesets from the AIX command line with the lslpp command, as shown in
Figure 18-12.
Figure 18-12 AIX lslpp command listing of the server installp images
8. Lastly, we repeat all of these processes on the other cluster node.
18.3 Configuration for clustering
Now we provide details about the configuration of the Veritas Cluster Server,
including the configuration of the Tivoli Storage Manager server as a highly
available application.
We will prepare the environments prior to configuring this application in the VCS
cluster, and ensure that the Tivoli Storage Manager server and client
communicate properly prior to HA configuration.
VCS will require start, stop, monitor, and clean scripts for most of the
applications. Creating and testing these prior to implementing the Service Group
configuration is a good approach.
754 IBM Tivoli Storage Manager in a Clustered Environment
18.3.1 Tivoli Storage Manager server configuration
In 17.5, “VCS pre-installation” on page 723, we prepared the needed storage,
network, and volume resources. We now utilize these resources during the Tivoli
Storage Manager server configuration, and develop the start and stop scripts to
be used by the VCS cluster:
1. First, we remove the entry from /etc/inittab on both nodes, which auto starts
the IBM Tivoli Storage Manager server, StorageAgent, and ISC, using the
rmitab autosrvr command, as shown in Example 18-1.
Example 18-1 The AIX rmitab command
banda:/# rmitab autosrvr
banda:/# rmitab autostgagnt
banda:/# rmitab iscn
Atlantic:/# rmitab autosrvr
Atlantic:/# rmitab autostgagnt
Atlantic:/# rmitab iscn
2. We stop the default server installation instance, if running, as shown in
Example 18-2. Using the kill command (without the -9 option) will shut down
the Tivoli Storage Manager server process and the associated threads.
Example 18-2 Stop the initial server installation instance
# ps -ef|grep dsmserv
root 41304 176212 0 09:52:48 pts/3 0:00 grep dsmserv
root 229768 1 0 07:39:36 - 0:56 /usr/tivoli/tsm/server/bin/dsmserv quiet
# kill 229768
3. Next, we set up the appropriate IBM Tivoli Storage Manager server directory
environment setting for the current shell issuing the following commands, as
shown in Example 18-3.
Example 18-3 The variables which must be exported in our environment
# export DSMSERV_CONFIG=/tsm/files/dsmserv.opt
# export DSMSERV_DIR=/usr/tivoli/tsm/server/bin
4. Then, we clean up the default server installation files which are not required,
and must be completed on both nodes. We will remove the default created
database, recovery log, space management, archive, and backup files
created. We also remove the dsmserv.opt and dsmserv.dsk files which will be
located on the shared disk. These commands are shown in Example 18-4.
Chapter 18. VERITAS Cluster Server on AIX and IBM Tivoli Storage Manager Server 755
Example 18-4 Files to remove after the initial server installation
# cd /usr/tivoli/tsm/server/bin
# mv dsmserv.opt /tsm/files
# mv dsmserv.dsk /tsm/files
# rm db.dsm
# rm spcmgmt.dsm
# rm log.dsm
# rm backup.dsm
# rm archive.dsm
5. Next, we configure IBM Tivoli Storage Manager to use the TCP/IP
communication method. See the Installation Guide for more information on
specifying server and client communications. We verify that the
/tsm/files/dsmserv.opt file reflects our requirements.
6. Then we configure the local client to communicate with the server, (only basic
communication parameters in dsm.sys found in the /usr/tivoli/tsm/client/ba/bin
directory). We will use this initially for the Command Line Administrative
Interface. This configuration stanza is shown in Example 18-5.
Example 18-5 The server stanza for the client dsm.sys file
* Server stanza for admin connection purpose
SErvername tsmsrv04_admin
COMMMethod TCPip
TCPPor 1500
ERRORLOGname /usr/tivoli/tsm/client/ba/bin/dsmerror.log
7. Allocate the IBM Tivoli Storage Manager database, recovery log, and storage
pools on the shared IBM Tivoli Storage Manager volume group. To
accomplish this, we will use the dsmfmt command to format database, log,
and disk storage pool files on the shared file systems. This is shown in
Example 18-6.
Tip: For information about running the server from a directory different from
the default database that was created during the server installation, see the
Installation Guide, which can be found at:

Get IBM Tivoli Storage Manager in a Clustered Environment now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.