Preparing for aggregate backup

You need to consider the following items as you prepare for aggregate backup:
  • Minimizing data set contention on your system.

    When ABACKUP is processing data sets on level 0 volumes and the status of a data set changes (for example, it is moved or deleted) after the list of data sets to process has been created but before backup processing has begun, ABACKUP processing fails. Then ABACKUP processing must be entirely rerun.

  • Specifying data sets in one or more selection data sets so they can be processed by aggregate backup
  • Writing instructions and useful information in an optional instruction data set
  • Defining an aggregate group to identify the selection data sets, instruction data set, and other control information for aggregate backup
  • Defining a management class
  • Defining aggregate backup environmental options with the SETSYS command
  • Using RACF® facility class to authorize certain users or operators to issue the ABACKUP command

Table 1 shows a checklist you might want to follow as you complete each of the steps needed to prepare for and perform aggregate backup.

Table 1. Aggregate Backup Checklist
Step Action
___ 1. Negotiate with the recovery site to provide the support required to recover your data sets.
___ 2. Review z/OS Planning for Installation.
___ 3. Define the aggregate group to identify the selection data sets, the instruction data set, and any additional control information.
___ 4. Define the management class.
___ 5. Create the selection data sets that list the data sets to be processed by aggregate backup. See z/OS DFSMShsm Implementation and Customization Guide, Chapter 4, under the heading Data Mover Support for Availability Management Functions for a list of data set types that are supported for aggregate backup.
  1. Allocate the selection data sets.
  2. Enter an INCLUDE list of the data sets to be backed up. This step is optional; however, if you omit an INCLUDE list, you must at least specify an ALLOCATE or ACCOMPANY list.
  3. Enter an EXCLUDE list of the data sets that should not be backed up. This step is optional.
  4. Enter an ACCOMPANY list of the tape data sets that should be taken with the aggregate backup data file and should be cataloged at the recovery site. This step is optional.
  5. Enter an ACCOMPANYEXCLUDE list of data sets you want excluded from the ACCOMPANY list. This step is optional.
  6. Enter an ALLOCATE list of data sets you want only allocated and cataloged at the recovery site. This step is optional.
  7. Enter an ALLOCATEEXCLUDE list of data sets you do not want allocated and cataloged at the aggregate recovery site. This step is optional.
___ 6. Create an instruction data set to contain any helpful information or instructions for the recovery site. This is optional.
___ 7. Link-edit the aggregate backup installation exits. This step is optional.
___ 8. Ensure that all level 0, ML1, and ML2 DASD volumes containing the data sets referred to for aggregate backup are online.
___ 9. Ensure that the ABARS JCL procedure was installed in the systems JCL library (refer to the z/OS DFSMShsm Implementation and Customization Guide).
___ 10. Determine the SETSYS parameters to be used:
  • Specify maximum number of ABARS address spaces
  • Specify activity log type, message level, and deletion processing
  • Specify whether output tapes should be stacked or not
  • Specify whether you want the ABARS FSR record written as an SMF record
  • Specify how DFSMSdss backs up level 0 DASD during ABACKUP processing
  • Indicate ABARS procedure name
  • Indicate TAPESECURITY(RACF) if you have decided to use RACF TAPEVOL tape security.
  • Specify TAPESECURITY(EXPIRATION) if RACF DATASET security is to be used.
  • Activate desired installation exits
  • Specify ABARS buffer usage
___ 11. Add the aggregate backup procedure name defined by SETSYS ABARSPROCNAME to the RACF started task table.
___ 12. Use RACF FACILITY class to authorize certain users or operators to issue the ABACKUP command.
___ 13. If you want to RACF protect output tape volumes, you can issue the SETSYS command with the TAPESECURITY(RACF) parameter and issue the RACF command RDEFINE TAPEVOL HSMABR; or you can instead use RACF DATASET class profiles to protect the tapes and create the DATASET profiles using ADDSD
___ 14. Issue the ABACKUP command with the VERIFY parameter.
  • If aggregate backup verification completes successfully (RC=0), continue to step 16.
  • If aggregate backup verification fails, correct any errors and repeat this step until the aggregate backup verification completes with a return code of zero.
___ 15. Issue the ABACKUP command with the EXECUTE parameter.
___ 16. Review the activity log for messages ARC6060I and ARC6061I that list the aggregate backup control and data files volumes. The control file volume serial numbers are required as input for aggregate recovery.