Multiple nodes can be used to perform backup operations
using the scheduler.
When you grant proxy authority to the agent nodes, they
perform scheduled backup operations on behalf of the target node.
Each agent node must use the asnodename option within
their schedule to perform multiple node backup for the agent node.
Start
the schedules using dsmc sched client command:
The
following examples show the administrative client-server commands
using the scheduler on multiple nodes.
- The administrator registers all of the nodes to be used by issuing
the following commands:
- register node NODE-A
- register node NODE-B
- register node NODE-C
- The administrator grants proxy authority to each agent node using
the following commands:
- grant proxynode target=NODE-Z agent=NODE-A
- grant proxynode target=NODE-Z agent=NODE-B
- grant proxynode target=NODE-Z agent=NODE-C
The administrator
defines the schedules using the following commands:- define schedule standard proxy1 description="NODE-A proxy
schedule" action=incremental options="-asnode=NODE-Z" objects=/Volumes/Xsan1
startdate=05/21/2005 starttime=01:00
- define schedule standard proxy2 description="NODE-B proxy
schedule" action=incremental options="-asnode=NODE-Z" objects=/Volumes/Xsan2
startdate=05/21/2005 starttime=01:00
- define schedule standard proxy3 description="NODE-C proxy
schedule" action=incremental options="-asnode=NODE-Z" objects=/Volumes/Xsan3
startdate=05/21/2005 starttime=01:00
Note: Place the asnodename option in the schedule
definition only. Do not place it in the client options file, on the
command line, or in any other location.
For more information
about the server scheduler commands, see IBM Tivoli Storage
Manager Administrator Command Reference.
You can also
use the client acceptor daemon (
dsmcad), with
managedservices set
to
schedule in the systems options file.
Note: - Each schedule can be started from a different workstation or LPAR.
- After running the schedules, any proxied client can query and
restore all of the backed up data.