|
A typical FDRINC Volume Incremental Backup system consists of:
- Full-volume backups (usually taken once per week) where all data
on a volume is backed up.
- Incremental backups (usually taken once per day) where
only the changed data sets are backed up.
The backups created by FDRINC are fully “managed”, which means they are recorded and
tracked by an automated recording mechanism. From those managed backups, either the whole
volume or individual data sets can be easily restored.
- Restoring individual data sets...The most recent copy of a data set can be
restored by specifying just the data set name. Additional options are
available to allow older copies of the data set to be restored, if required.
- Recreating entire DASD volumes...If one or more volumes have been lost,
perhaps due to hardware problems or as a consequence of a disaster, these
volumes can be automatically recovered from a combination of their full and
incremental backups...
//BACKUP EXEC PGM=FDRABR,REGION=0M
//TAPE1 DD UNIT=3590-1,DSN=FDR1,DISP=(,KEEP),VOL=(,,,255)
//TAPE2 DD UNIT=3590-1,DSN=FDR2,DISP=(,KEEP),VOL=(,,,255)
//TAPE3 DD UNIT=3590-1,DSN=FDR3,DISP=(,KEEP),VOL=(,,,255)
//SYSIN DD *
DUMP TYPE=FDR,ONLINE,DSNENQ=USE,RTC=YES
EXCLUDE ALLDSN,VOLG=WORK
|
Some points to note about the above example job:
- The DUMP TYPE=FDR statement instructs ABR to take a full-volume dump
of the selected volumes.
- The combination of the ONLINE parameter (on the DUMP statement) and the subsequent
EXCLUDE statement instructs ABR to select all DASD volumes that are online to the
z/OS system, with the exception of the WORK volumes.
- Three TAPEx DD statements have been provided so that three disk volumes
will be concurrently dumped.
- As each tape drive becomes available at the end of backing up a DASD volume,
ABR will automatically piggyback the next disk volume as the next file on that
tape.
- The DSNENQ=USE parameter causes ABR to issue an informational message
for any dataset that was OPEN at the time of the backup. These
datasets will still be backed up.
- RTC=YES will significantly reduce the back elapsed
time by using READ TRACK CCWs to read disk data tracks.
- After the backup of each volume is completed and recorded,
the MVS Update Bits will be turned off for all datasets on the volume.
Using the simple job above, with a single control statement,
you could backup a large number of DASD volumes.
If disk failures occur, or if a DASD volume has to be restored at a disaster site, FDRINC automates
the volume restore process by locating the most recent set of full-volume and incremental backups.
It starts off the restore process by reading the most recently-created incremental, restoring the
label track, VTOC, VTOCIX, VVDS and any datasets on that backup. It then reads back through
the preceding incrementals and the full-volume backup, restoring the most recent copy of each
dataset—once only.
The result of this restore process is a volume that looks exactly like the original volume at the
time of the last backup, whether it was a full-volume or an incremental backup. All the datasets
are in their original locations, with the exact same allocation characteristics.
The following example job shows the JCL and control statements required to
recover a disk volume called PROD01 from the full-volume and incremental
backups. Notice how only the volser of PROD01 has been specified.
The DYNTAPE parameter tells FDRINC to identify from its control files the backup
tapes that are required to complete the restore.
The DISK1 DD points to the output volume that will be used for the restore (SPARE1) and
the CPYVOLID=YES tells FDRINC to rename SPARE1 to PROD01 after the contents
of PROD01 have been restored to it.
//RESTFULL EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//DISK1 DD UNIT=3390,VOL=SER=SPARE1,DISP=OLD
//SYSIN DD *
RESTORE TYPE=FDR,CPYVOLID=YES,DYNTAPE
SELECT VOL=PROD01,NVOL=SPARE1
|
 return to top
|
|
|
| Can we HELP you... |
|
Looking for more information?
|
USER STORY:
Ameren migrates 10TB of storage to new volumes without interruption with FDRPAS
Read more
USER STORY:
A Sound Investment – Citigroup tames its backup environment with dedicated mainframes
Read more
|
