IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

The nodes have the following qualities:v NodeA owns the cluster resource with file systems /A1 and /A2v NodeB owns the cluster resources with file systems /B1 and /B2v NodeC owns the cluster resources with file systems /C1 and /C2Note: NodeA might also have two non-clustered volumes, /fs1 and /fs2, that mustbe backed up.For best backup performance, you might want all nodes in the cluster to performthe backups of the shared file systems that they own. When a node failover occurs,the backup tasks of the failed node shift to the node to which the failoveroccurred. For example, when NodeA fails over to NodeB, the backup of /A1 and /A2moves to NodeB.The following are prerequisites before configuring the backup-archive client toback up cluster and non-cluster volumes:vvvA separate backup-archive client scheduler process must be run for eachresource group being protected. In normal conditions, each node would havetwo scheduler processes: one for the cluster resources, and one for the local filesystems. After a failure, additional scheduler processes are started on a node inorder to protect the resources that have moved over from another node.The backup-archive client password files must be stored on cluster disks so thatafter a failure, the generated backup-archive client password is available to thetakeover node.The file systems to be protected as part of a resource group are defined usingthe backup-archive client domain option. The domain option is specified in thedsm.sys file, which should also be stored on a cluster disk so that it can beaccessed by the takeover node.Follow the steps below to configure the Tivoli Storage Manager backup-archiveclient in a cluster environment.1. Register backup-archive client node definitions on the Tivoli Storage ManagerServer. All nodes in the cluster must be defined on the Tivoli Storage ManagerServer. If you are defining multiple cluster resources in a cluster environmentto failover independently, then unique node names must be defined perresource group. For the above sample three-way active/active clusterconfiguration, define three nodes (one per resource), as follows: (1) tsm:IBM>register node nodeA nodeApw domain=standard, (2) tsm: IBM>registernode nodeB nodeBpw domain=standard, (3) tsm: IBM>register node nodeCnodeCpw domain=standard.2. Configure the backup-archive client system options file. Each node in thecluster must have separate server stanzas for each cluster resource group inorder to be backed up in each respective dsm.sys file. You must ensure thatthe server stanzas are identical in the system option files on each node.Alternatively, you can place the dsm.sys file on a shared cluster location. Theserver stanzas defined to back up clustered volumes must have the followingspecial characteristics:vThe nodename option must refer to the client node name registered on theTivoli Storage Manager Server. If the client node name is not defined, thenode name will default to the host name of the node, which might conflictwith other node names used for the same client system.Recommendation: Use the nodename option to explicitly define the clientnode.Chapter 2. Configuring the Tivoli Storage Manager client 69