BackBox H4.00 VTC Scripting Option

Script controller
2 BackBox H4.00 VTC Scripting Option
Note that this feature targets environments where numerous scripts are submitted,
and where the back-end Enterprise Backup server saves BackBox Windows files on
physical sequential media.
In simple setups, the retry mechanism is likely to be the only interesting feature.
This mechanism does not rely on return codes to detect errors, but checks the actual
result of a restore or backup by accessing the Windows file after the script execution:
A file was successfully restored if it is present.
A file was successfully saved if the file’s archive bit (the Windows file system
attribute) was reset, or if the file is no longer present. The file is assumed to
have been archived in the later case.
The VTC emulator is not aware of the usage of the script controller, and
communicates the requests to the regular script as usual by Windows parameters,
refer to the setup of regular backup/restore scripts in the Configuration chapter.
To enable the script controller, the user must:
update the regular scripts:
o Update the backup script, replacing the Enterprise Backup client command by
a BBBACKUP command.
o Update the restore script, replacing the Enterprise Backup client command by
a BBRESTORE command
create a backup and a restore sub-script:
o the subscript will be started by the script manager
o the subscript runs the Enterprise Backup client; it uses a temporary file
(%BBOX_FILELIST%) that contains the name of files to process
o Requirement: the execution of backup sub-script must either delete the
archived file, or reset the Archive bit of the file in the Windows file-system.
Most Enterprise backup software are able to do so, some requires
configuration to reset the Archive bit on files successfully backed up.