Air Cleaner User Manual

Chapter 15. Integrating to IBM Tivoli Storage Manager
SysBack version 5.6 and later allows for the storage of backup objects into an IBM
Tivoli Storage Manager server. Backups to a TSM server may be manipulated like
any other SysBack backup. They may be listed, verified, restored, and used for
system reinstallation.
Combining the SysBack backup, restore, and network boot / install functions with
a TSM server provides bare metal recovery capability for TSM configurations.
SysBack will back up and recover a system’s volume group, logical volume, and
file system information. Optionally, SysBack will back up any non-rootvg data
specified. SysBack may be used as a stand alone backup and recovery solution.
However, some customers may opt to use SysBack simply to recover the rootvg
volume group and then use TSM to backup and manage other user data.
Prerequisites, Limitations, and Exclusions
The hardware and operating system requirements for storing backups into a TSM
server are the same as the base product as defined in “System Requirements” on
page 1-1. The following additional requirements are specific to interactions with
TSM:
v A previously configured TSM server must be at level 5.1.5 or higher
v The 32-bit TSM API client must be installed and at level 5.1.5 or higher
v The TSM node name used for SysBack backups must be registered on the TSM
server and configured to use thepasswordaccess generateoption.
v Only JFS and JFS2 file systems are supported for all of the backup types
v The File / Directory backup type may also be used to backup CD-ROM and
NFS file systems
v All backup, restore, list, verify, and query operations must be performed as the
root user
The following limitations and exclusions apply to interaction with TSM:
v SysBack should not be used to backup TSM HSM managed file systems. You
will need to explicitly specify any HSM managed file system in the SysBack
exclude list. For detailed information on SysBack exclude lists, please refer to
Chapter 9, “Exclude Lists”, on page 9-1.
Note: Using SysBack to back up HSM managed file systems will cause all of the
migrated data to be recalled for the backup operation. This could cause
lengthy backup times. Also, there may not be enough space in the file
system to recall all of the migrated data. Use the TSM Backup / Archive
Client to backup HSM file systems instead.
v LAN Free backups are not supported
v COMMMethod TCPIP is the only supported TSM communication method
v GPFS file systems are not supported
Note: The TSM Backup / Archive Client supports the backup of GPFS file
systems.
v Veritas file systems are not supported
© Copyright IBM Corp. 2002,2003 15-1