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.

Setting up encryptionThere are some steps you must follow to set up encryption with theencryptkey=save option.1. Specify encryptkey=save in the options file.2. Back up at least one file with asnode=ProxyNodeName to create a localencryption key on each agent node in the multiple node environment.Follow these steps to set up encryption with the encryptkey=prompt option:1. Specify encryptkey=prompt in the options file.2. Ensure that users of the agent nodes in the multiple node environment areusing the same encryption key.Important:v If you change the encryption key, you must repeat the previous steps.v Use the same encryption key <strong>for</strong> all files backed up in the shared nodeenvironment.Scheduling with client-node proxy supportMultiple nodes can be used to per<strong>for</strong>m backup operations using the scheduler. Bygranting proxy authority to the agent nodes, they will per<strong>for</strong>m scheduled backupoperations on behalf of the target node. Each agent node must use the asnodenameoption within their schedule to per<strong>for</strong>m multiple node backup <strong>for</strong> the agent node.The following examples show the administrative client-server comm<strong>and</strong>s using thescheduler on multiple nodes.1. The administrator registers all of the nodes to be used: (1) register nodeNODE-A, (2) register node NODE-B, (3) register node NODE-C.2. The administrator grants proxy authority to each agent node: (1) grantproxynode target=NODE-Z agent=NODE-A, (2) grant proxynode target=NODE-Zagent=NODE-B, (3) grant proxynode target=NODE-Z agent=NODE-C.3. The administrator defines the schedules: (1)define schedule st<strong>and</strong>ard proxy1description="NODE-A proxy schedule" action=incrementaloptions="-asnode=NODE-Z" objects=/Volumes/Xsan1 startdate=05/21/2005starttime=01:00, (2) define schedule st<strong>and</strong>ard proxy2 description="NODE-Bproxy schedule" action=incremental options="-asnode=NODE-Z"objects=/Volumes/Xsan2 startdate=05/21/2005 starttime=01:00, (3) defineschedule st<strong>and</strong>ard proxy3 description="NODE-C proxy schedule"action=incremental options="-asnode=NODE-Z" objects=/Volumes/Xsan3startdate=05/21/2005 starttime=01:00.Note: Place the asnode option in the schedule definition only. Do not place it inthe 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.Note:134 <strong>IBM</strong> <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> <strong>for</strong> <strong>UNIX</strong> <strong>and</strong> <strong>Linux</strong> <strong>Backup</strong>-<strong>Archive</strong> Clients Version 6.1: Installation <strong>and</strong> User’s Guide

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

Saved successfully!

Ooh no, something went wrong!