A backup set is a collection of backed-up data from one client, which is stored and managed as a single object on specific media in server storage. The server creates copies of active versions of a client's backed up objects that are within the one or more file spaces specified with the GENERATE BACKUPSET command, and consolidates them onto sequential media.
Currently, the backup object types that are supported for backup sets include directories, files, and image data. If you are upgrading from Tivoli® Storage Manager Express®, backup sets can also contain data from Data Protection for Microsoft SQL and Data Protection for Microsoft Exchange servers. The backup set process is also called instant archive.
You can generate backup sets on the server for individual client nodes or for groups of nodes. A node group is a group of client nodes that are acted upon as a single entity. If you specify one or more node groups, the server generates a backup set for each node and places all of the backup sets together on a single set of output volumes. To create a node group, use the DEFINE NODEGROUP command, and then use the DEFINE NODEGROUPMEMBER command to add nodes to the group. For details, see the Administrator's Reference. The client node for which a backup set is generated must be registered to the server.
Centera storage devices do not support backup sets.
Administrators can generate multiple copies of backup sets that correspond to some point-in-time. The backup sets can be retained for various time periods. This is an efficient way to create long-term storage of periodic backups, without requiring the data to be sent over the network again.
While an administrator can generate a backup set from any client's backed up files, backup sets can only be used by a backup-archive client.
You cannot generate a backup set with files that were backed up to Tivoli Storage Manager by using NDMP. However, you can create a backup set with files that were backed up using NetApp SnapShot Difference.
When generating backup sets, the server searches for active file versions in an active-data storage pool associated with a FILE device class, if such a pool exists. For details about the complete storage-pool search-and-selection order, see Selection for active file versions.
Data from a shred storage pool will not be included in a backup set unless you explicitly permit it by setting the ALLOWSHREDDABLE parameter to YES in the GENERATE BACKUPSET command. If this value is specified, and the client node data includes data from shred pools, that data cannot be shredded. The server does not issue a warning if the backup set operation includes data from shred pools. For more information about shredding, see Securing sensitive client data .