12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1. Each schedule can be started from a different machine or LPAR.2. After running the schedules, any proxied client will be able to query <strong>and</strong>restore all of the backed up data.Scheduling <strong>for</strong> backing up a HACMP clusterThis section shows some examples of how to back up a HACMP cluster.In the following examples, HACMP is configured <strong>for</strong> two AIX hosts, host_a <strong>and</strong>host_b. Along with their own local data, the hosts are sharing disk storage whichhas two file spaces: /disk1 <strong>and</strong> /disk2.The CLUSTERNODE example shows how the clusternode option is used in acurrent HACMP environment.1. The administrator defines 3 nodes on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server:host_a, host_b, cluster_group, using the following comm<strong>and</strong>s: (1) REGISTERNODE host_a mysecretpa5s, (2) REGISTER NODE host_b mysecretpa5s, (3)REGISTER NODE cluster_group mysecretpa5s.2. The administrator defines a dsm.opt file on host_a <strong>and</strong> host_b (note that theopt files are different on each host), using the following comm<strong>and</strong>s: (1)NODENAME host_a (option can be left as default), (2) DOMAIN /home /usr ...etc..3. The administrator defines a dsm.opt file located somewhere on one of thecluster disk groups, <strong>for</strong> example, /disk1/tsm/dsm.opt, using the followingcomm<strong>and</strong>s: (1) NODENAME cluster_group, (2) DOMAIN /disk1 /disk2, (3)CLUSTERNODE YES.4. The administrator defines a schedule on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server,using the following comm<strong>and</strong>: DEFINE SCHEDULE STANDARD CLUSTER_BACKUP.5. The administrator defines associations <strong>for</strong> each of the 3 nodes, using thefollowing comm<strong>and</strong>: DEFINE ASSOC STANDARD CLUSTER_BACKUPhost_a,host_b,cluster_group. At any one time, there are three instances of the<strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> <strong>Backup</strong>-<strong>Archive</strong> client schedule running (with thescheduler <strong>for</strong> cluster_group being part of the cluster resources that willfailover whenever the cluster group disk resources failover. Thus, it would berunning on either host_a or host_b but not both simultaneously).6. All three node names contain data on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server.The ASNODE example shows a generic solution which could be applied to <strong>UNIX</strong>cluster solutions to which we do not have support, <strong>for</strong> example: Veritas ClusterServer <strong>for</strong> Solaris.1. The administrator defines 3 nodes on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server host_a,host_b, cluster_group:REGISTER NODE host_a mysecretpa5sREGISTER NODE host_b mysecretpa5sREGISTER NODE cluster_group mysecretpa5s2. The administrator defines a proxy node relationship between host_a <strong>and</strong>host_b to hacmp_clusterGRANT PROXYNODE TARGET=cluster_group AGENT=host_a,host_b3. The administrator defines a dsm.opt file on host_a <strong>and</strong> host_b to h<strong>and</strong>le thelocal file systems:NODENAME host_a (option can be left as default)DOMAIN /home /usr ... etc.NODENAMEDOMAINhost_b (option can be left as default)/home /usr ... etc.Chapter 4. Backing up your data 135

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!