Scheduling backups with client-node proxy support

When you grant proxy authority to the agent nodes, they perform scheduled backup operation 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.

Perform the following steps to enable scheduling of multiple nodes:

1. Ensure that all agent nodes must have proxy authority over the common target node
2. 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 <agentnodename>

The following examples show the administrative client-server commands using the scheduler on multiple nodes.

• The administrator registers all 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, by issuing 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, by issuing the following commands:
  • define schedule standard proxy1 description="NODE-A proxy schedule" action=incremental options="-asnode=NODE-Z" objects=C: startdate=05/21/2005 starttime=01:00
  • define schedule standard proxy2 description="NODE-B proxy schedule" action=incremental options="-asnode=NODE-Z" objects=D: startdate=05/21/2005 starttime=01:00
  • define schedule standard proxy3 description="NODE-C proxy schedule" action=incremental options="-asnode=NODE-Z" objects=E: startdate=05/21/2005 starttime=01:00

Start the schedules by either configuring a scheduler service, or by using the following client command: dsmc sched