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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note: Place the asnode option in the schedule definition only. Do not place itin the client options file, on the comm<strong>and</strong> line, or in any other location.For more in<strong>for</strong>mation about the server scheduler comm<strong>and</strong>s, see <strong>IBM</strong> <strong>Tivoli</strong> <strong>Storage</strong><strong>Manager</strong> Administrator Comm<strong>and</strong> Reference.Start the schedules using the following client comm<strong>and</strong>:dsmc schedYou can also use the client acceptor daemon (dsmcad), with managedservices set toschedule in the systems options file.Notes: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 GPFS filesystemThe following examples show the administrative client server comm<strong>and</strong>s using thescheduler to back up a GPFS filesystem, using three nodes in the GPFS clusterwhich participate in the backup.1. The administrator defines four nodes on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server:node_1, node_2, node_3 <strong>and</strong> node_gpfs. node_1, node_2 <strong>and</strong> node_3 are onlyused <strong>for</strong> authentication; all filespaces are stored with node_gpfs.REGISTER NODE node_1 mysecretpa5sREGISTER NODE node_2 mysecretpa5sREGISTER NODE node_3 mysecretpa5sREGISTER NODE node_gpfs mysecretpa5s2. The administrator defines a proxynode relationship between the nodes:GRANT PROXYNODE TARGET=node_gpfs AGENT=node_1, node_2, node_33. The administrator defines the node name <strong>and</strong> asnode name <strong>for</strong> each of themachines in their respective dsm.sys files:nodename node_1asnodename node_gpfs4. The administrator defines a schedule <strong>for</strong> only node_1 to do the work:DEFINE SCHEDULE STANDARD GPFS_SCHEDULE ACTION=MACROOBJECTS="gpfs_script"DEFINE ASSOCIATION STANDARD GPFS node_gpfs5. To execute the schedule on node node_gpfs, enter the client comm<strong>and</strong>:DSMC SCHEDAnother way to back up GPFS is to use <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> to look <strong>for</strong> theincremental changes. The GPFS filesystem can be divided into three branches <strong>and</strong>each branch can be statically assigned to each node using the virtualmountpointoption. In the following example, you have a file system called /gpfs with threebranches: /gpfs/branch_1, /gpfs/branch_2, <strong>and</strong> /gpfs/branch_3.1. The administrator defines four nodes on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server:node_1, node_2, node_3 <strong>and</strong> node_gpfs. node_1, node_2 <strong>and</strong> node_3 are onlyused <strong>for</strong> authentication; all filespaces are stored with node_gpfs.REGISTER NODE node_1 mysecretpa5sREGISTER NODE node_2 mysecretpa5sREGISTER NODE node_3 mysecretpa5sREGISTER NODE node_gpfs mysecretpa5s2. The administrator defines a proxynode relationship between the nodes:GRANT PROXYNODE TARGET=node_gpfs AGENT=node_1,node_2,node_3Chapter 4. Backing up your data 99

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

Saved successfully!

Ooh no, something went wrong!