Installation and User's Guide

vUse the same encryption key for all files backed up in the shared nodeenvironment.Scheduling backups with client-node proxy supportMultiple nodes can be used to perform backup operations using the scheduler.When you grant proxy authority to the agent nodes, they perform scheduledbackup operation on behalf of the target node. Each agent node must use theasnodename option within their schedule to perform multiple node backup for theagent node.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 The following examples show the administrative client-server commands using thescheduler on multiple nodes.vThe administrator registers all the nodes to be used, by issuing the followingcommands: (1) register node NODE-A, (2) register node NODE-B, (3) registernode NODE-C.v The administrator grants proxy authority to each agent node, by issuing thefollowing commands: (1) grant proxynode target=NODE-Z agent=NODE-A, (2)grant proxynode target=NODE-Z agent=NODE-B, (3) grant proxynodetarget=NODE-Z agent=NODE-C.v The administrator defines the schedules, by issuing the following commands: (1)define schedule standard proxy1 description="NODE-A proxy schedule"action=incremental options="-asnode=NODE-Z" objects=C:startdate=05/21/2005 starttime=01:00, (2) define schedule standard proxy2description="NODE-B proxy schedule" action=incrementaloptions="-asnode=NODE-Z" objects=D: startdate=05/21/2005 starttime=01:00,(3) define schedule standard proxy3 description="NODE-C proxy schedule"action=incremental options="-asnode=NODE-Z" objects=E:startdate=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 command line, or in any other location.For more information about the server scheduler commands, see IBM Tivoli StorageManager Administrator Command Reference.Start the schedules by either configuring a Tivoli Storage Manager scheduleservice, or by using the following client command: dsmc schedYou can also use the client acceptor daemon, with managedservices set to schedulein the systems options file.Important:v Each schedule can be started from a different workstation or LPAR.Chapter 4. Backing up your data 121