Volume Backup Examples


All examples in this section are found in the JCL library installed with FDR. The member names are EX5020x.

Full volume dump all volumes example

Take full-volume backups of all DASD volumes at the installation, except WORK volumes. Three TAPEx DD statements are provided, so three DASD volumes are concurrently dumped. VOL=(,,,255) is specified in case any individual DASD volume requires over five tapes. DSNENQ=USE causes ABR to print an FDR158 message for any data set that was in use at the time of the backup, but backs up the data set anyway (no abend occurs if data sets are in use).

As each tape drive becomes available at the end of backing up a volume, ABR piggybacks the next DASD volume as the next file on that tape. By default, ABR puts up to 255 backup files on a tape volume (or multi-volume tape set) before dismounting it and starting on a new tape. If this still leaves unused space on your high-capacity tape drives, you can add the MAXFILE= operand to increase the limit (up to 65534).

//BACKUP   EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//SYSPRIN2 DD SYSOUT=*
//SYSPRIN3 DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//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,ENQERR=NO,RTC=YES
 EXCLUDE ALLDSN,VOLG=WORK
/*

Important

The data set names on the TAPEx DD statements are dummy names supplied to satisfy the rules of JCL. ABR generates the data set names for the backup files.

Full volume dump certain volumes with zEDC example

Take full-volume backups of all SYS and PROD volumes, dumping two volumes concurrently, and making two copies of each backup invoking the zEnterprise Data Compression feature. The TAPE11 and TAPE22 DD statements contain COPY2 backups identical to the COPY1 backups on TAPE1 and TAPE2. The VTOCs of each DASD volume are enqueued and reserved during the backups. ABR only dumps the used portion of PS or PO data sets.

//BACKUP   EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//SYSPRIN2 DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD UNIT=TAPE,DISP=(,KEEP),VOL=(,,,255),DSN=FDR1
//TAPE11   DD UNIT=TAPE,DISP=(,KEEP),VOL=(,,,255),DSN=FDR11
//TAPE2    DD UNIT=TAPE,DISP=(,KEEP),VOL=(,,,255),DSN=FDR2
//TAPE22   DD UNIT=TAPE,DISP=(,KEEP),VOL=(,,,255),DSN=FDR22
//SYSIN    DD *
 DUMP     TYPE=FDR,ENQ=RESERVE,DATA=USED,COMPRESS=ALL,ZEDC=YES
 MOUNT    VOLG=SYS
 MOUNT    VOLG=PROD
/*


Important

ABR V5.4L83 supports full volume backup of VM and Linux volumes. For more information, see ABR Backup of z/VM and Linux Volumes.

Incremental backup all online volumes example

An incremental backup of all online DASD volumes is done to two tape drives. Two DASD volumes are processed concurrently, creating multiple backup data sets on the tapes (one per DASD volume). All data sets on the DASD volumes that have been updated since the last ABR full-volume or incremental backup of that volume are selected. However, all data sets with the text “PAYROLL” anywhere in their name are backed up regardless of their update status. All data sets selected are printed in ABR VTOC format. The ABRBKDQ points to the ABR backup dump remote queue data set; if present, any queued requests for backup are processed.

//BACKUP   EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//SYSPRIN2 DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD UNIT=3590-1,DSN=FDR1,DISP=(,KEEP),VOL=(,,,255)
//TAPE2    DD UNIT=3590-1,DSN=FDR2,DISP=(,KEEP),VOL=(,,,255)
//SYSIN    DD *
 DUMP     TYPE=ABR,ONLINE,PRINT=ABR,RTC=YES
 SELECT   DSN=**PAYROLL**
/*
//ABRBKDQ  DD DSN=FDRABR.ABRBKDQ.DATA,DISP=SHR

Backup only selected data sets example

Do a manual backup (TYPE=DSF) of certain data sets using tape hardware compression. The combination of ONLVOL and CATDSN= causes only the volumes on which those data sets are cataloged to be processed. Using catalog data set name filtering (see Generic-Data-Set-Name-Selection), all ISPF data sets for “USERnn” and the current generation of any “GLEDGER” GDGs are dumped. A listing of the selected data sets in ABR PRINT VTOC format is printed.

Even though this is a TYPE=DSF backup, the backup files created are part of the ABR backup subsystem. They are assigned a cycle number in the current generation of the volumes involved, and are read if an ABR full-volume restore is required. FDRAPPL Application Backup (Working-with-FDRAPPL) is a better technique for dumping selected data sets.

//DSF      EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//ABRMAP   DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=FDR,DISP=(,KEEP),UNIT=CART,DCB=TRTCH=COMP
//SYSIN    DD *
 DUMP     TYPE=DSF,ONLVOL,PRINT=ABR,RTC=YES
 SELECT   CATDSN=USER++.**ISPF**
 SELECT   CATDSN=GLEDGER.**(0)
/*

Automatic incremental or full volume backup example

Do an incremental backup of all updated data sets on all online DASD volumes (same as DUMP TYPE=ABR), except that ABR forces a full-volume dump for any selected volume if the number of incremental backups in the current generation exceeds the limit specified for CYCLE in the ABR Model DSCB. TAPE1 and TAPE2 cause two DASD volumes to be dumped concurrently, and TAPE11 and TAPE22 cause duplicate backups to be created. Incremental and full-volume backups are mixed on the same set of tapes.

TYPE=AUTO can be used when you do not have a special time to do full-volume backups (such as weekends), but prefer to do full-volume dumps of certain volumes each night and incremental backups of the rest of the volumes. Once the cycle counts of the volumes have been synchronized so that only a selected subset of your volumes exceed their count each night, the process is automatic. If you do prefer to do full-volume backups on weekends or another special time, use separate jobs with TYPE=FDR and TYPE=ABR instead.

//BACKUP   EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//SYSPRIN2 DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD UNIT=CART,DSN=FDR1,DISP=(,KEEP)
//TAPE11   DD UNIT=CART,DSN=FDR11,DISP=(,KEEP)
//TAPE2    DD UNIT=CART,DSN=FDR2,DISP=(,KEEP)
//TAPE22   DD UNIT=CART,DSN=FDR22,DISP=(,KEEP)
//SYSIN    DD *
 DUMP     TYPE=AUTO,ONLINE,RTC=YES
/*

Full volume (or Incremental) backup to DASD example

Do a full volume (or incremental) dump of the PROD* volumes to DASD. Dumping to DASD is desired since the site has DASD replication technology to ensure DASD volumes are mirrored off-site, but does not have tape replication technology; thus, the backups to DASD are mirrored to the disaster recovery site automatically when dumped to DASD. This example shows a full-volume dump, TYPE=FDR, but can be changed to an incremental dump by specifying TYPE=ABR.

//FULLDUMP EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//SYSPRIN2 DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=FDRABR.POOLDISK.BACKUP1,
//            DISP=OLD,UNIT=SYSALLDA,RETPD=90,
//            VOL=SER=(OUTV01,OUTV02,OUTV03,OUTV04)
//TAPE2    DD DSN=FDRABR.POOLDISK.BACKUP2,
//            DISP=OLD,UNIT=SYSALLDA,RETPD=90,
//            VOL=SER=(OUTV05,OUTV06,OUTV07,OUTV08)
//TAPE11   DD DSN=FDR11,DISP=(,KEEP),RETPD=360,
//            UNIT=TAPE,VOL=(,,,255)
//TAPE12   DD DSN=FDR12,DISP=(,KEEP),RETPD=360,
//            UNIT=TAPE,VOL=(,,,255)
//SYSIN    DD *
 DUMP     TYPE=FDR,DSNENQ=USE,ENQERR=NO,
               COMPRESS=COPY1,DATA=USED
 MOUNT    VOLG=PROD
/*

Incremental backup of SMS-managed volumes example

Dump any updated data sets from all volumes in two SMS storage groups, creating backups on one tape drive.

//BACKSMS  EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DSN=FDRSMS,UNIT=TAPE,DISP=(,KEEP),VOL=(,,,99)
//SYSIN    DD *
 DUMP     TYPE=ABR,SMSMANAGE=YES,RTC=YES
 MOUNT    STORGRP=DBLARGE
 MOUNT    STORGRP=DBSMALL
/*


Important

SMS-managed volumes can also be selected by normal DISKxxxx DD statements or VOL=/VOLG= operands. SMS management class attributes (see Working-with-System-Managed-Storage may be used to exclude certain data sets from backup.

Simulate incremental backup example

Simulate the incremental backup of all online volumes beginning with “TSO”. ABR reports on all updated data sets that would be selected by a real DUMP TYPE=ABR.

//SIM      EXEC PGM=FDRABR,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSPRIN1 DD SYSOUT=*
//ABRMAP   DD SYSOUT=*
//SYSSUMM  DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//TAPE1    DD DUMMY
//SYSIN    DD *
 SIM      TYPE=ABR,RTC=YES
 MOUNT    VOLG=TSO
/*

 

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