Air Cleaner User Manual

Be aware that using the same TSM node name for both the TSM Backup / Archive
Client client and the SysBack backup client will show different file space results
than if they were separate. Please see the example below.
tsm> query filespace Num Last Incr Date Type
File Space Name --- -------------- ----
--------------- 1 00/00/00 00:00:00 API:TSMVFS
/TSM4SBR 2 00/00/00 00:00:00 JFS
/home/tempvg2fs1
All backups created with SysBack will have a file space type of API:TSMVFS and a
file space name of /TSM4SBR. SysBack However, backups created using the TSM
Backup / Archive Client will have a file space type denoted by type of file system
where the backup data resided, and the file space name will be the root of that file
system or virtual mount point name.
Binding and Rebinding Backups to TSM Management Classes
Binding Backups
Binding is a TSM term that refers to associating a file with a management class.
When a backup is performed, the backup objects (images) are either bound to the
default management class for the active policy set, or the objects are bound to the
management class specified in your include / exclude list.
Include statements are used to bind an object to a management class other than the
default management class. The include statements are either placed directly in the
/usr/tivoli/tsm/client/api/bin/dsm.sys file or into an include / exclude file
referenced by the specified server stanza in the dsm.sys file.
Include statements to bind SysBack backups to a non-default management class are
a little different than the usual TSM include statements. There are only 5 possible
include statements that affect the binding of backups initiated by Sysback.
They are:
INCLUDE /TSM4SBR/SB/* FullSystemBackupClass
INCLUDE /TSM4SBR/VG/* VolumeGroupBackupClass
INCLUDE /TSM4SBR/LV/* LogicalVolumeBackupClass
INCLUDE /TSM4SBR/FS/* FilesystemBackupClass
INCLUDE /TSM4SBR/FD/* FileDirectoryBackupClass
These include statements bind an entire backup type to a management class. For
example, the Full System Backup is comprised of a table of contents image and
several logical volumes images that represent the data of raw logical volumes and
/ or logical volumes that have mounted file systems. Each and every image
created by a single backup operation, whether it be 5 or 20 images, will be bound
to the same management class. Backup images are grouped by TSM so that all
components of a single backup operation will expire at the same time based on the
management class attributes.
Chapter 15. Integrating to IBM Tivoli Storage Manager 15-17