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
Guidelines
4 BackBox H4.00 VTC Scripting Option
For Tivoli Storage Manager (TSM), be sure to install the TSM Backup command line
client “dsmc” that will be fetched by the scripts.
The TSM Administrative client command line “dsmadmc”, along an Administrative
client name authorized to queries only, has two potential usages:
o For massive concurrent restores directly accessing TSM sequential media, the
TSM Administrative client can be programmatically used by the BackBox
Script Controller to optimize the restores scripts, grouping scripts accessing
the same TSM physical media.
o The NonStop operator who manages the NonStop backups gets some
autonomy, for example to query the available TSM storage space and the
state of specific virtual volumes.
***
One of these for distributed sets of scripts is suggested.
Script\TSM\WithController_TSM_CachedArchive\*.*
Script\TSM\WithoutController_TSM_CachedArchive \*.*
Script\TSM\WithController_TSM_Archive\*.*
Script\TSM\WithoutController_TSM_Archive \*.*
In the versions with “….Cached…”, the archived files version are kept on disk for a
limited period configured by the “Deleted Backed Up files” parameters in the Volume
groups.
In the versions without “…Cached…, TSM deletes immediately a file successfully
archived.
In the versions “…WithController…”, the BackBox Script controller is enabled for
retries and batching. This is recommended for setups where a sequential media is
directly accessed by backups or restores, such as LAN-FREE setups, and especially
when massive, concurrent backups or restore are executed.
In the version “…WithoutController…”, simple scripts are executed. This is
recommended for simplicity in setups that access only TSM disk pools, or marginally
run concurrent backups or restores.
***
The scripts save the files in “Archives” objects rather than “Backups” objects.
Archives are more appropriate as the backup multiple versions of an object does not
make sense with virtual volumes.
The TSM Management Class must be configured for the Archive Copy Group, and the
retention should be infinite – as the BackBox “delete script” will delete the Archive
when the corresponding virtual volume has expired in DSM/TC or in other NonStop
catalogs supported for the Auto-Scratch enabled in the Volume Group.