BackBox H4.00 VTC Scripting Option

Introduction
5 BackBox H4.00 VTC Scripting Option
Enabling or not the Script controller
There are two processing modes for the scripts.
1. The first mode corresponds to a simpler setup, where there is one execution
of the script for each virtual volume.
2. The second set is used when scripts are managed by the Script controller. In
this case, the first level of scripts just forward backup or restore requests to
the VTC Script Controller. These requests are then queued and managed by
the Script Controller. When a batch is submitted by the Script Controller, a
distinct sub-script is executed to process a variable number of volumes,
whose file names are received in a file list.
In both cases, the first level of scripts looks identical, they are identified in the Data
Store advanced configuration page. User parameters can also be defined and their
value set in the same page.
The Script controller is described in the last chapter of this manual. It is a batch
sub-system used for two reasons:
• Retries: When the user wants another layer of error recovery on top of
whatever retries the Enterprise Backup clients implement. By default, the
Script controller will retry for 24 hours, with a delay of 5 minutes before a
retry.
• Serialization: A VTC typically implements several virtual tape drives and
might trigger several concurrent scripts. The number of concurrent script
executions might be limited by the Enterprise backup software, or just
because the Enterprise backup client accesses directly a sequential media,
such as a physical tape library, and the number of drives in the tape library is
very limited. The script controller queues the backup or restore requests,
consolidate similar requests together and submit them in a configured
number of queues and threads per queue.