BackBox H4.00 VTC Scripting Option
Table Of Contents
- Table of Contents
- Introduction
- Scripts in VTCs
- Script execution cases
- Enabling or not the Script controller
- Overview of script implementation
- Guidelines
- Script settings in the BackPak UI
- Detailed description
- Script controller

Script settings in the BackPak UI
5 BackBox H4.00 VTC Scripting Option
Link Back up all non backed-up files
The backup script is normally automated and if enabled, the script controller
will automatically retry failed backups. Files marked as not backed up are
usually either still being backed up or in the script controller input queue.
This button is for re-submitting manually the backup scripts that have failed
for reason unrelated to the software like communication or power failures.
Notice that the Script controller (the script contains the BBBACKUP
command) contains its own retry mechanism; in this case the manual retry is
required only after the controller stops retrying, such as after a VTC reboot.
When the “Storage Route” is set for a specific VTC, the scripts will be
submitted only to this VTC.
When the “Storage Route” is set for “1
st
available VTC” the scripts will be
distributed depending on preferences according the volume information
available in the domain:
- First, the VTC which contains the Windows files of the volume will
be preferred. The VTC is supposed to contain the volume if the last
known file location has an UNC syntax, such as \\svr1\share1, and
the server name part is equal to the VTC tcpip address or to the
last known VTC hostname.
- Second, the VTC who has written the Windows files is preferred.
- In the preferred VTC is not reachable by TCPIP, does not contain
the backup script, or is not able to submit the script, another route
will be tried.










