Full Volume RESTORE Statement


RESTORE statement syntax

RESTORE

TYPE=FDR


,CLOUD=cloudname


,CONFMESS=NO|YES


,CONTAINER=FDR.ABR.BACKUP|cloudcontainer


,COPY=n


,CPYVOLID=NO|YES


,DYNTAPE


,DYNTAPE2


,EXPDT=yyddd|yyyyddd


,MAXCARDS=100|nnnnn


,MAXDD=nnnn


,MAXERR=20|nnnn


,ONLINE|ONLVOL


,OPERATOR


,SMSPROT=ALL|NONE


,VOLRESET=NO|YES

RESTORE statement

The RESTORE TYPE=FDR statement performs a full-volume recovery of one or more DASD volumes from ABR Volume Backups. Only one RESTORE statement is allowed per execution of ABR.

ABR full volume recovery procedure

ABR full-volume recovery reads a generation of Volume Backups, starting with an incremental backup (from which the VTOC, VTOCIX, and VVDS are restored, and any data sets backed up to that incremental). It then reads successive incremental backups in descending cycle order, restoring the most recent backup of each data track. Finally, it reads the full-volume backup that began the generation, restoring all data tracks which were not found on any of the incremental backups. The result is that the restored volume looks exactly as the volume did at the point of the first incremental backup read.

By default, ABR starts with the most recent incremental backup in the current generation, but if you want to restore to a different point-in-time, you can specify the cycle (incremental) to start with. You can even restore from an earlier generation. If the most recent incremental is a TYPE=DSF manual backup, it is automatically bypassed since it does not contain all the information required, such as VTOC, VTOCIX, and VVDS.

If you are performing this restore at a disaster recovery site, you must do a separate restore of the ABR catalog, since volume recovery depends on the current ABR catalog to get backup tape information. Although the ABR catalog is backed up as part of daily incremental backups, you cannot depend on this backup since it is done in the middle of ABR backups and does not contain the latest information for all volumes. See Disaster-Recovery for suggestions on the procedures to follow.

Important

If data sets have been excluded from incremental backups, they are not restored to the most current level, unless they have been unchanged since the full-volume backup at the beginning of the generation. This is true if the data set was excluded using the protect list or EXCLUDE statement.

Warning

Before you do a full-volume restore, make sure that the target volume is offline to all systems other than the system where the restore is to be run. If you do not, the other systems may access the original VTOC of the restored volume and access or delete the wrong data.

Simulated full volume recovery

SIMREST is not supported with TYPE=FDR. If you wish to see which backup volumes FDR needs to restore a given DASD volume, use program FDRABRP with the statement PRINT CATLG,VOL=vol (see FDRABRP-Catalog-Report).

FDRDRP

FDRDRP is a full-volume restore program, with the same result as an ABR full-volume restore, but it manages the backup tapes to minimize tape mounts and reduce the elapsed time of the restores. Normal ABR full-volume restore does one DASD volume at a time, and may mount an input tape multiple times. FDRDRP does many DASD volumes in parallel and mounts input tapes a minimum number of times (often only once). FDRDRP documentation is included in this manual, starting in Section 50.80 “FDRDRP.

RESTORE statement operands

TYPE=FDR

Required for a full volume restore. It is followed by one or more SELECT statements, each specifying a volume to be recovered.

CLOUD=

cloudname

the name of the cloud where the restore is directed.

CONFMESS=
NO

Suppresses the WTOR and begins the restore immediately.

YES

Before beginning the restore, FDR requests confirmation via a WTOR FDRW01 message to which the z/OS operator must reply.

Default: YES.

Important

CONFMESS=NO can be useful at a disaster recovery site to avoid delaying full volume restores while waiting for an operator response.

CONTAINER=

cloudcontainer

The name of the container in the cloud where the backup is stored. The name must start with the HLQ of FDR.

Default: FDR.ABR.BACKUP

COPY=

n

Specifies the copy (1 to 9) of the backup from which the restore is to be done. COPY=2 can be specified if a duplicate tape copy (TAPExx) was created at backup time. Copies 2 through 9 can be created by the FDRTCOPY or FDRTSEL utility (see FDR-and-ABR-Backup-Maintenance).

If COPY=1 or 2 and ABR finds that one of the backup tapes is not cataloged under the copy specified, ABR checks to see if the other copy was created. If cataloged, ABR uses the other copy. So, if the specified copy has expired (and been uncataloged by a tape management system) ABR automatically uses the other copy (1 or 2) if it still exists.

Default: COPY=1 unless overridden in the FDR Global Options.

CPYVOLID=

Specifies whether the volume serial number of the DASD volume that was backed up is restored, if the existing volume serial number of the output DASD volume is different (if the serials are the same, CPYVOLID= is ignored).

NO

The volume serial number of the output volume is retained. See VOLRESET= in Full-Volume-Restore-Examples.

YES

Volume serial number of the output volume is replaced with the original volume serial number of the DASD volume that was dumped. If another online volume has the same serial, the restored volume is placed offline at the end of the restore.

Default: NO, unless the volume being restored was SMS-managed, when “YES” is forced.

Important

Although full-volume ABR restore does not catalog data sets, any data sets that were cataloged to the original volume are automatically cataloged to the new volume when restoring with CPYVOLID=YES, assuming that you restore the system catalogs to the same point-in-time. If you use CPYVOLID=NO and do not later relabel the volume, data sets may need to be manually recataloged.

DYNTAPE
DYNTAPE2

Specifies that ABR is to dynamically allocate the backup data sets using a ddname of TAPE#. Use this option if the backup is on DASD, in an Automated Tape Library (ATL) or a mix of backup device types is read, such as 3490E or 3590. Do not use DYNTAPE and TAPEDD= in the same execution.

DYNTAPE2 allocates two drives which improves performance when restoring from multi-volume tape backups on 3480 cartridges. Do not use DYNTAPE2 if backup files on DASD might be involved.

DYNTAPE and DYNTAPE2 deallocate the tape drive if the restore of the next DASD volume in this ABR step does not need the same tape volume. If the same tape volume is required for the restore of the next DASD volume, it remains mounted.

Default: The first TAPEx DD statement found in the step JCL is used to mount all backups, unless TAPEDD= was specified.

EXPDT=

Specifies an expiration date that is passed to OPEN when each backup file is opened. Since these are input tapes, the expiration date is probably ignored by your tape management system except for certain special dates. The most common use is EXPDT=98000, which is accepted by most tape management systems and means, “this tape is not in the tape management database”. You might need to use EXPDT=98000 (or whatever your TMS supports) when the tape management database has not been restored to a point after the ABR backups were taken, so that it does not reflect the backup tapes that FDRDRP needs to read. In this case, it might be easier to disable tape management until the database can be made current. If you use a TAPEx DD statement (instead of DYNTAPE), you can also specify the EXPDT= operand on the DD statement. The value on the DD statement overrides this operand if both are specified.

The date is specified in Julian format with a 2-digit year “yyddd” or a 4-digit year “yyyyddd”. If the 2-digit year is used, year numbers less than 70 are assumed to be in the 21st Century (for example, 20355 = 2020.355).

MAXCARDS=

nnnnn

Enables ABR to accept additional SELECT, EXCLUDE, and MOUNT statements during this execution. You can specify values up to 65535, but values over 100 increase the region required by ABR.

Default: 100 SELECT, EXCLUDE, and MOUNT statements.

MAXDD=

Specifies the maximum number of DASD volume serials that ABR can process in this step. ABR builds its volume list from DISKxxxx DD statements and/or ONLINE volumes if ONLINE is coded. Once this limit is reached additional volumes are ignored. If you code ONLINE, MAXDD= (or its default) must be larger than the number of online DASD volumes, even if they are not being restored.

Default: 256 volumes, unless overridden by the MAXONLINE option in the FDR Global Options (see MAXONLINE in ABR-Options).

MAXERR=

nnnn

Specifies the number of tape or DASD errors (1 to 9999) that, if reached, cause the operation to abend. Each error is indicated by a message and possible mini-dump.

Default: 20.

ONLINE
ONLVOL

Allows ABR full-volume restore to restore to online DASD volumes without requiring DISKxxxx DD statements for them. The required output volumes (identified by VOL= or NVOL= operands) are dynamically allocated when needed. See MAXDD= in Full-Volume-Restore-Examples.

ONLINE

Specifies that ABR is to process every volume that is online to the system; if there are more than 255 online volumes, you need to specify MAXDD= to increase that limit (See MAXDD= in Full-Volume-Restore-Examples).

ONLVOL

Specifies that ABR is to scan all SELECT statements for the operands VOL=, VOLG=, or CATDSN= (for volume selected from the catalog). These volumes, if online, are appended to the ABR volume list.

OPERATOR

Specifies that before the RESTORE operation began, an operator message is issued for each tape necessary to complete the restore. This operand gives the operator the ability to pre-pull required tapes or bypass individual cycles for which the tapes may not be available at this time. However, if some cycles are bypassed, the restore may not correctly restore the latest version of some data sets.

SMSPROT=
ALL

Enforces several rules when SMS-managed volumes are involved. Backups of SMS-managed volumes can only be restored to SMS-managed volumes, and non-SMS volumes only to non-SMS volumes. CPYVOLID=YES is forced when an SMS-managed volume is restored.

NONE

Allows the restore of SMS-managed volumes to non-SMS volumes, and vice versa. Also allows the restore of SMS-managed volumes to new volume serial numbers if CPYVOLID=NO is specified.

Default: ALL.

Warning

Use SMSPROT=NONE with caution. It is usually used at a disaster recovery site where a re-IPL of z/OS is done after the restores, to place all volumes in the proper SMS status. See System-Managed-Storage-SMS for more details on restoring and moving SMS-managed volumes.

VOLRESET=

NO

Do not do any of the processing listed for VOLRESET=YES. All data sets are restored with the names they have on the backup and the ABR Model DSCB is restored unmodified.

YES

If CPYVOLID=NO is specified or defaulted, and the volume serial of the output DASD is different from that of the original DASD on the backup, the volume serials that are part of the data set names of the VTOC Index (SYS1.VTOCIX.volser), the VVDS (SYS1.VVDS.Vvolser) and the ABR Model DSCB (usually FDRABR.Vvolser) are checked to see if they match the input volume serial (the volume backed up). If so, they are renamed to match the volume serial number of the output DASD. Also, the DSCB field DS1DSSN (data set serial number, usually the volume serial number of the first or only volume of the data set) for every data set on the volume is changed to the new volume serial if the existing value matched the original volume serial.

Regardless of the value of CPYVOLID=, the ABR Model DSCB on the restored volume is set so that the next incremental backup of the volume creates the next cycle number in the current generation for that volume. (A restore using TAPEDD= sets the cycle number to 63 to force the next backup to be a full-volume backup and increment the generation number).

Important

  • If you intend to restore the backup to a new permanent volume serial, use CPYVOLID=NO with VOLRESET=YES. Data sets on the volume are not recataloged to the new volume serial, but you can catalog them using the IDCAMS “DEFINE” command (VSAM must be recataloged with DEFINE CLUSTER RECATALOG and SMS non-VSAM data sets must be recataloged using DEFINE NONVSAM RECATALOG). See the IBM IDCAMS manual for syntax details.
  • If you intend to restore the backup to a temporary volume serial but later relabel it back to the original volume serial (from the backup), use CPYVOLID=NO with VOLRESET=NO.

Default: YES.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*