Recovery From a Quiesced Backup

Backup and Recovery › Manual Recovery › Recovery From a Quiesced Backup

Recovery From a Quiesced Backup

Quiesced Backup

A quiesced backup is a backup that is performed while no updates are being made to the data that is being copied. The following types of backup are quiesced backups:

A backup performed after the DC/UCF system is shutdown
A backup performed while the DC/UCF system is active, provided that the affected areas are quiesced at the time of the backup
A backup performed before and after a local mode job

Note: For more information about how to backup a database, see see 21.2, “Backup Procedures”.

Recovery Procedure

The procedure outlined below describes the general approach to recovery from a quiesced backup. See the later sections in this chapter for additional considerations specific to certain types of failures.

Action	Steps
Copy the files that need to be recovered from the backup When required: Always.	Execute the RESTORE utility statement using the FILE option or another comparable utility.
Consolidate, in the sequence in which they were created, the archive journal files created since the quiesce point established at the start of the backup procedure. When required: This step is necessary only under the following conditions: In z/OS environments, if the subsequent ROLLFORWARD utility statement will be executed with the SEQUENTIAL option and more than one archive journal file must be processed. In a data sharing environment, if more than one member has updated the affected areas and the subsequent ROLLFORWARD utility statement will be executed with either the SEQUENTIAL or the ALL and STOP TIME options.	Execute one of the following and use as input the properly concatenated set of archive files: FIX ARCHIVE utility statement MERGE ARCHIVE utility statement EXTRACT JOURNAL utility statement another comparable utility If consolidating archive files from multiple members and the subsequent rollforward will be executed with either the SEQUENTIAL or the ALL and STOP TIME options, use the MERGE ARCHIVE utility statement. Note: For more information, see 21.11, “Data Sharing Recovery Considerations”. If recovery involves local mode journal files, the MERGE ARCHIVE utility statement can be used to consolidate both local mode journal files and archive files. Note: For more information, see 21.10, “Recovery Procedures for Mixed-Mode Operations”.
Reapply to the restored files all updates made since the backup was taken When required: Always.	Execute the ROLLFORWARD utility statement using either the consolidated journal file or individual archive files concatenated in the sequence in which they were created. If the journal files were consolidated using the EXTRACT JOURNAL utility, specify the FROM EXTRACT option. If FROM EXTRACT is not specified, then the following considerations apply: Specify the SORTED option unless there is insufficient disk space available. SORTED must be specified if: A consolidated journal file is not used as input in z/OS environments and more than one archive file must be processed. The input journal file is on a device, such as a disk or a 3490 that does not support reading backwards. Running ROLLFORWARD in a z/VM environment. If the SEQUENTIAL option is used and the quiesce point for the affected areas does not coincide with the start of the first input file, use the START TIME parameter to identify the quiesce point.

Action

Steps

Copy the files that need to be recovered from the backup

When required: Always.

Execute the RESTORE utility statement using the FILE option or another comparable utility.

Consolidate, in the sequence in which they were created, the archive journal files created since the quiesce point established at the start of the backup procedure.

When required: This step is necessary only under the following conditions:

In z/OS environments, if the subsequent ROLLFORWARD utility statement will be executed with the SEQUENTIAL option and more than one archive journal file must be processed.

In a data sharing environment, if more than one member has updated the affected areas and the subsequent ROLLFORWARD utility statement will be executed with either the SEQUENTIAL or the ALL and STOP TIME options.

Execute one of the following and use as input the properly concatenated set of archive files:

FIX ARCHIVE utility statement
MERGE ARCHIVE utility statement
EXTRACT JOURNAL utility statement
another comparable utility

If consolidating archive files from multiple members and the subsequent rollforward will be executed with either the SEQUENTIAL or the ALL and STOP TIME options, use the MERGE ARCHIVE utility statement.

Note: For more information, see 21.11, “Data Sharing Recovery Considerations”.

If recovery involves local mode journal files, the MERGE ARCHIVE utility statement can be used to consolidate both local mode journal files and archive files.

Note: For more information, see 21.10, “Recovery Procedures for Mixed-Mode Operations”.

Reapply to the restored files all updates made since the backup was taken

When required: Always.

Execute the ROLLFORWARD utility statement using either the consolidated journal file or individual archive files concatenated in the sequence in which they were created.

If the journal files were consolidated using the EXTRACT JOURNAL utility, specify the FROM EXTRACT option.

If FROM EXTRACT is not specified, then the following considerations apply:

Specify the SORTED option unless there is insufficient disk space available. SORTED must be specified if:
A consolidated journal file is not used as input in z/OS environments and more than one archive file must be processed.
The input journal file is on a device, such as a disk or a 3490 that does not support reading backwards.
Running ROLLFORWARD in a z/VM environment.

If the SEQUENTIAL option is used and the quiesce point for the affected areas does not coincide with the start of the first input file, use the START TIME parameter to identify the quiesce point.