Processing redirected restore in batch mode

Backup Object Manager provides a redirected restore batch mode function where the TDI for the target database is modified before it starts the redirected restore.

About this task

The TDI image to be used must be available as an ASCII file in the file system. For example, a TDI image that is created during an interactive redirected restore can be used as target TDI for a redirected restore in batch mode. Batch mode can also be used for multiple redirected restores to different locations with identical changes of the physical database structure. As with the interactive mode, the original TDI is used to test whether the changes of table space container sizes and locations that are made are valid. In addition, modifications to the sizes of all or selected table space containers of the target database can be made to optimize the I/O performance. Backup Object Manager provides automated table space resizing and automated table space normalizing for these modifications.

Before a redirected restore in batch mode is started, the TDI for the target database must be available. This scenario is accomplished by providing the target TDI image of a previous interactive redirected restore as a file in the file system or by retrieving the original TDI from Tivoli® Storage Managerr. Issue the following command to retrieve a TDI image from Tivoli Storage Manager into the file system: 
backom -c r_tdi -a DB2 source alias -t timestamp -d target directory of TDI
This original TDI image can be renamed and modified.
Issue the following command on the target system to run a redirected restore in batch mode: 
backom -c rr_db_batch -a DB2 source alias,DB2 target alias -t <timestamp,...
...-f full qualified path and name of target TDI file
Backup Object Manager performs these steps during a redirected restore in batch mode:
  1. Backup Object Manager replaces the alias that is specified in the target TDI file with the alias of the target database. If no target database alias is specified, Backup Object Manager uses the original database alias as the target database alias.
  2. Backup Object Manager retrieves the original TDI from Tivoli Storage Manager and verifies whether the target TDI defines table space containers that are sufficient to replace the original table space containers.
  3. Backup Object Manager uses the target TDI and the original TDI to run basic plausibility checks.
  4. Backup Object Manager uses the target TDI to create the necessary table space containers on the target system. If the target database alias is the same as the original database alias, the database is restored to the original database alias and SID. When Backup Object Manager restores to the original system, it attempts to overwrite the original database. Overwriting the original database requires approval by the administrator.
  5. Backup Object Manager calls the DB2® redirected restore function.