Restoring data set backups

Use RUV backups for files needing automated recovery. The backups are automatically registered and can be automatically selected when recovery is needed.

RUV can restore any backup that it has taken. You may need to restore a file to a particular historical point in time. RUV provides the information you need to determine the correct backup to use to restore the data to the point in time that you want.

If RUV has no active backup of the specified VSAM file registered in its repository, by default it attempts to restore the most recent SMS backup.

For RUV to restore another vendor's backup, the backup must be written in key sequence in IDCAMS-standard format (flat-file format). Also, to allow RUV to automatically detect another vendor's backup file, the file must be registered in the RUV repository. When the vendor's backup is not registered to RUV, you must use the other vendor's product to find the backup. You must use the other vendor's process for restoring the file.

RUV rebuilds alternate indexes after a successful restore.

The forward recovery process automatically invokes the restore process if a VSAM data set does not exist in the z/OS catalog. In this case, RUV selects the most current backup that is allowed by the BACKUP_METHOD keyword. The default is BACKUP_METHOD(RUV BWO SNAPSHOT SMS EXTERNAL).

If the backup was created by RUV as an Instant Snapshot copy, the restore of the data set is instantaneous.

Restoring files with RUV involves determining which VSAM files to restore, building the JCL for the restore job, building the RUV command for each file you want to restore, running the restore job, and reviewing the results of the restore job.