StorageTek 6 manual Restore Utility, Reasons for Running the RESTore Utility, Prerequisites

Restore

Restore Utility

The RESTore utility provides a way to re-create the library control data set from a previous backup copy of the data set. You also have the option to apply all journals (maximum of 99 files per run) since the last backup, if journaling is enabled.

Caution: It is critical that you restore all data sets referenced by the HSC (primary, secondary, standby). Failing to restore all data sets can cause CDS mismatches. Refer to “Control Data Set Recovery” on page 58 and “Reassigning Control Data Set Names in Database Heartbeat Record” on page 60 for additional information.

Prerequisites

Warning: The host software must be stopped on all hosts and the SCP must be operational when this utility is executed.

Reasons for Running the RESTore Utility

The RESTore utility performs the following tasks:

•re-creates the library control data set from a backup copy

•applies contents of any journals having activity since the backup. This process occurs only if you have designated that journals are enabled. See ‘‘SLIRCVRY Macro’’ in the HSC Installation Guide for information about enabling journaling.

Notes: The HSC BACKup and RESTore utilities can be used as part of a procedure to rename control data sets. Refer to “Reassigning Control Data Set Names in Database Heartbeat Record” on page 60 for detailed information on renaming control data sets.

How the RESTore Utility Functions

The RESTore utility is executed in the following phases:

•A hardware reserve is issued against the control data set.

•The library control data set is restored from a previous backup copy.

•If journaling is enabled, the installation optionally can apply journals (up to 99 files per run) to the restored library control data set. It is the user’s responsibility to include all journals and offload copies made since the last backup.

•The restored library control data set is duplicated in the secondary and standby control data sets if secondary and standby control data sets are being used. Refer to “Control Data Set Recovery” on page 58 for additional information about the control data set recovery scheme.

•If GENerate (YES, Only, or Short) is specified in the RESTore JCL, output of the discrepancies encountered is stored in the SLSAUDIT data set. For information on resolving any discrepancies, see ‘“How to Handle BACKup/RESTore Discrepancies” on page 283.

•The control data set is released, and the utility ends.

276VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601