102 Tivoli Storage Manager V6.1 Technical Guide
In Tivoli Storage Manager V5.x, the log was circular. As such, the notion of how much log
would be freed up by a database backup had significance because it implied that the log was
healthy and the tail of the log could be moved up to free some amount of space based on the
database backup.
With Tivoli Storage Manager V6, the log is no longer circular, so the need to free a specific
amount of log space during a database backup is no longer significant. Database backup with
Tivoli Storage Manager V6.1 is oriented more toward protecting the database than was
previously the case.
While the V5 database backup triggers are no longer supported, Tivoli Storage Manager still
triggers automatic backups. Depending on which trigger is met, a full or an incremental
backup is executed.
5.4.2 Restoring the database
If a database is damaged or destroyed and a database backup and other files are available,
the database can be restored. In addition to just preparing for a disaster, you can also use the
restore process to distribute your database and or log volumes to different file systems
available to your Tivoli Storage Manager server.
Figure 5-31 explains the new process flow for a restore of the Tivoli Storage Manager server
Figure 5-31 V6.1 database restore process flow
V6 DB Restore Process Flow
Sequential Data Stream
(Disk Devc or Tape)
Initiate DB2 restore
Intercept inbound session from DB2
1 Retrieve volume history information
TSM API, node
Initiate database restore
Chapter 5. IBM Tivoli Storage Manager database 103
Three types of database restore operations are supported:
Restoring the database to its most current state
Restoring the database to a point in time
Restoring the database from a snapshot
In this section we provide an example of a restore scenario and show which requirements to
meet for a successful restore.
Restore prerequisites
To restore your database, the following information is required:
You must have copies of the volume history file and the device configuration file.
You must have copies of, or you must be able to create, the server options file and the
database and recovery log setup information (the output from detailed queries of your
database and recovery log).
The server needs information from the volume history file. Volume history information is
stored in the database, but during a database restore, it is not available from there. It is critical
that you make a copy of your volume history file and save it. The file cannot be recreated.
The database volumes we created with the database backup from Example 5-29 on page 93
are listed by the volume history file as shown in Example 5-36.
Example 5-36 Volume history file content
* Sequential Volume Usage History
* Updated 06/04/2009 09:30:23
Operation Date/Time: 2009/06/12 14:51:29
* Location for volume G:\TSM\SERVER1\FILECLASS\44843491.DBV is: ''
Database Backup LLA: FULL_BACKUP.20090612145129.1
Database Backup HLA: \NODE0000\
Volume Name: "G:\TSM\SERVER1\FILECLASS\44843491.DBV"
Backup Series: 5
Backup Op: 0
Volume Seq: 1
Device Class Name: FILE
Database Backup ID: 0 , 3073
Database Backup Home Position: 0
Database Backup Total Data Bytes : 0 , 381800459
Database Backup Total Log Bytes: 0 , 13656075
Database Backup Log Block Number: -1 , -1
Operation Date/Time: 2009/06/12 14:51:29
* Location for volume G:\TSM\SERVER1\FILECLASS\44843516.DBV is: ''
Database Backup LLA: FULL_BACKUP.20090612145129.2
Database Backup HLA: \NODE0000\
Volume Name: "G:\TSM\SERVER1\FILECLASS\44843516.DBV"
Backup Series: 5

Get Tivoli Storage Manager V6.1 Technical Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.