BackBox H4.00 VTC Scripting Option

Guidelines
1 BackBox H4.00 VTC Scripting Option
Guidelines
Cross system restores
The restore script, as well as the other scripts, must be implemented in a way that
any VTC configured as route to the Data Store can execute it, whatever the VTC that
originally wrote the disk files storing a virtual volume, including VTC servers that
Massive jobs through concurrent NonStop drives
If there is a possibility of massive job, running several concurrent NonStop backups
or restores accessing sequential media in the Enterprise Backup, the process must
be planned carefully planned.
In the Enterprise Backup, there might be limited concurrent availability of tape drives
and contention on the un-sharable sequential media.
The backup part is usually solved by a Backup Enterprise writing first on disk, before
migrating to tapes in an efficient process.
***
For backing up, it is possible to write in parallel on several back-end media.
Restoring is more difficult as the reading of a NonStop volume requires a very
specific Backup Enterprise media. All other NonStop restores needing the same back-
end not sharable media will have to wait the restore script of the first NonStop
restore completes before their own script gets the needed media and begins
executing.
These contentions get worse because the number of NonStop virtual drives are
usually more numerous than the number of tape drives in the Enterprise Backup.
In both cases, the BackBox Script Controller can help by serializing the execution of
scripts.
The backup problem is generally solved by staging first on disk inside the Enterprise
Backup.
The restore is more difficult. A solution is to restore massively the image of ‘all
needed volumes’ requiring a very large disk space. Not counting the difficulty to
identifying ‘all volumes’.
Tight control and organization of the Enterprise Backup storage pool is required. The
content of back-end media must be planned – including the expiration process.
Specific extensions have been developed for TSM in the Script Controller, essentially
query the TSM server to know the back-end media needed for a NonStop volume,
then sort the execution of restore scripts by back-end media.
See in the Script Controller chapter.