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

#export DSM_CONFIG=/A1/tsm/dsm.opt#dsmc query sessionThe prompt for the password might appear at this time, but this isunlikely. If you are prompted, the password was not stored in the sharedlocation correctly. Check the passworddir option setting used for NodeA andfollow the configuration steps again.c. Ensure that the schedules are run correctly by each node. You can trigger aschedule by setting the schedule’s start time to now. Remember to reset thestart time after testing is complete.tsm: IBM>update sched standard clus_backup starttime=nowd. Failover and fallback between nodeA and nodeB, while nodeA is in themiddle of the backup and the schedule’s start window, is still valid. Verifythat the incremental backup will continue to run and finish successfullyafter failover and fallback.e. Issue the command below to cause a node’s (nodeA) password to expire.Ensure that backup continues normally under normal cluster operations, aswell as failover and fallback:tsm: IBM>update node nodeA forcep=yes9. Configure the backup-archive client to back up local resources.a. Define client nodes on the Tivoli Storage Manager Server. Local resourcesshould never be backed up or archived using node names defined to backup cluster data. If local volumes that are not defined as cluster resourceswill be backed up, separate node names (and separate client instances)must be used for both non-clustered and clustered volumes.In the following example, assume that only NodeA has local file systems/fs1 and /fs2 to be backed up. In order to manage the local resources,register a node NodeA_local on the Tivoli Storage Manager server: tsm:IBM>register node nodeA_local nodeA_localpw domain=standard.b. Add a separate stanza in each node’s system options file dsm.sys thatmust back up local resources with the following special characteristics:vvThe value of the tcpclientaddress option must be the local host name orIP address. This is the IP address used for primary traffic to and fromthe node.If the client will back up and restore non-clustered volumes withoutbeing connected to the cluster, the value of the tcpclientaddress optionmust be the boot IP address. This is the IP address used to start thesystem (node) before it rejoins the cluster:Example stanza for NodeA_local:Servername clinton_nodeA_localnodenamenodeA_localcommmethod tcpiptcpport 1500tcpserveraddress clinton.ibm.comtcpclientaddres nodeA_host.ibm.compasswordaccess generatemanagedservices schedulec. Define the user options file dsm.opt in a path that is on a non-clusteredresource.v The value of the servername option must be the server stanza in thedsm.sys file which defines parameters for backing up non-clusteredvolumes.v Use the domain option to define the non-clustered file systems to bebacked up.Chapter 2. Configuring the Tivoli Storage Manager client 73