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

4. The administrator defines a dsm.opt file on the cluster resource to handle thebackup of the clustered resources, e.g. /disk1/tsm/dsmcluster.opt (note thenodename will be the default nodename which will either be host_a or host_bdepending on which machine contains the cluster group at any given time):DOMAIN /disk1 /disk2ASNODE cluster_group5. The administrator defines a schedule on the Tivoli Storage Manager server:DEFINE SCHEDULE STANDARD CLUSTER_BACKUP6. The administrator defines associations for each one of the 3 nodes.DEFINE ASSOC STANDARD CLUSTER_BACKUP host_a,host_b,cluster_group7. At any one time, there are three instances of the Tivoli Storage ManagerBackup-Archive client schedule running with the scheduler for nodehacmp_cluster running on either host_a or host_b but not both (it is includedin the cluster resources that would failover). This scheduler would point to thedsmcluster.opt that is defined on each host. The three instances would bestarted as:[host_a] dsmc sched[host_b] dsmc sched[cluster_group] dsmc sched -optfile=/disk/tsm/dsmcluster.opt8. All three node names will contain data on the Tivoli Storage Manager server.For more information about the server scheduler commands, see IBM Tivoli StorageManager Administrator Command Reference.Perform the following steps to enable scheduling of multiple nodes:1. Ensure that all agent nodes must have proxy authority over the common targetnode2. Ensure that all agent nodes must have a schedule defined on the server:def sched domain_name sched_name options='-asnode=target'3. Ensure that each agent node must have its schedule associated with a node:def association domain_name schedule_name Scheduling for backing up a GPFS file systemThe following examples show the administrative client-server commands using thescheduler to back up a GPFS file system, using three nodes in the GPFS clusterwhich participate in the backup.1. The administrator defines four nodes on the Tivoli Storage Manager server,using the following commands: (1) REGISTER NODE node_1 mysecretpa5s, (2)REGISTER NODE node_2 mysecretpa5s, (3) REGISTER NODE node_3 mysecretpa5s,(4) REGISTER NODE node_gpfs mysecretpa5s. node_1, node_2, node_3 andnode_gpfs. node_1, node_2, and node_3 are only used for authentication; all filespaces are stored with node_gpfs.2. The administrator defines a proxynode relationship between the nodes, usingthe following commands: GRANT PROXYNODE TARGET=node_gpfs AGENT=node_1,node_2, node_3.3. The administrator defines the node name and asnodename for each of themachines in their respective dsm.sys files, using the following commands: (1)nodename node_1, (2) asnodename node_gpfs.4. The administrator defines a schedule for only node_1 to do the work, using thefollowing commands: (1) DEFINE SCHEDULE STANDARD GPFS_SCHEDULEACTION=MACRO OBJECTS="gpfs_script", (2) DEFINE ASSOCIATION STANDARD GPFSnode_gpfs.136 IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Version 6.1: Installation and User’s Guide