Air Cleaner User Manual

Rebinding Backups
Rebinding is a TSM term that refers to reassigning a backup to a different
management class. When a backup type is rebound to a different management
class, only the currently active backup, and all future backup operations after the
management class is changed, will be rebound.
For example, let us assume that you performed full system backups on Monday,
Tuesday, and Wednesday using the default management class. Then, on Thursday
you assigned a new management class to the full system backup using an include
statement. When the Thursday backup is initiated, the Thursday backup and the
Wednesday backup will be rebound to the new management class.
Excluding Objects from Backups
In order to exclude specified files, directories, logical volumes, or file systems from
backup processing, you must create an exclude list. The exclude list is created from
within SysBack. TSM exclude statements located in a dsm.sys file will not be
processed by SysBack backup commands. For more information regarding SysBack
exclude lists, please refer to Chapter 9, “Exclude Lists”, on page 9-1.
Restoring Backups from a TSM Server
Initiating restore operations from a TSM server is just like performing any other
SysBack restore. Restore operations are initiated by the usual restore commands.
However, rather than specifying a directory, tape, or CD / DVD drive as the
restore device, the TSM virtual device is specified. You must also specify the
unique backup id associated for the backup object that you would like to restore.
When performing a restore operation from within the SMIT interface, you will be
presented with a selection list that looks similar to the following:
Backup ID Type Active? Open? Management Class Backup Date
--------- ---- ------- ------- ------------------ -----------------
0.6684 FD No No DEFAULT 02/18/2003 13:07:
0.6686 FD Yes No DEFAULT 02/18/2003 13:08:
0.6679 LV Yes No DEFAULT 02/18/2003 13:06:
0.6659 SB Yes No DEFAULT 02/17/2003 14:54:
0.6673 VG Yes No DEFAULT 02/17/2003 15:31:
0.6636 FS Yes No DEFAULT 02/17/2003 13:53:
Note: The output is displayed by descending date regardless of backup type.
Within a date, the backups are grouped by type, and then by ascending time
stamp for each type.
For additional information regarding SysBack restore operations, please refer to
Chapter 10, “Recreating or Restoring from Backups”, on page 10-1.
Configuring Network Boot Options for a TSM Bare Metal Recovery
In order to perform a TSM bare metal recovery, the install client must initiate a
network boot in order to access the SysBack System Installation & Maintenance
Main Menus. For more information regarding the Installation and Maintenance
menus, please refer to Chapter 12, “System Installation and Maintenance”,on
page 12-1and to “Bare Metal Recovery and System Reinstallation from a TSM
Server” on page 15-21.
Network boot configuration procedures are performed like any other SysBack
network boot configuration. All of the same requirements apply with the following
additional requirements:
15-18 IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide