What can be done to improve the usability of backupsets ?
Each backupset occupies a full volume.
- If you store the backupset on a VTS, no space is wasted.
- If you are running more than one TSM server, then you can store backupsets as virtual volumes on another server. This way each backupset is considered an archive file on the target server and multiple backupsets can be stored on each physical volume.
- It is possible to use virtual volumes on a single TSM server. This requires the DRM feature, but could be an excellent solution. See appendix A for an example of how to do this.
Scheduling the generation of backupsets.
One way of scheduling backupsets is by inserting a number of "generate backupset..." commands into a server script and schedule the execution of this script. If you have 4 or more drives available, you can utilize more than one script and thus run the processes in parallel. But, it is your responsibility to keep the scripts updated with new nodes and balancing the nodes between scripts to best utilize your drives.
