Using non-intrusive journal backup

There are two types of journal backup methods which should be considered: quiesced and non-intrusive.

During quiesced journal backup, all DFSMShsm activity is quiesced while the journal and the control data sets are backed up.

During non-intrusive journal backup, all DFSMShsm activity is allowed to continue while DFSMShsm creates a backup of the preexisting journal records. After the initial backup of the journal completes, all DFSMShsm activity is quiesced and DFSMShsm completes the backup of the journal and backs up the control data sets using concurrent copy (this is a requirement of non-intrusive journal backup). The overall elapsed time for non-intrusive journal backup is approximately the same as quiesced journal backup.

Because all DFSMShsm activity is quiesced during quiesced journal backup, user and production jobs that require recall or recovery resources wait until the entire CDS and journal backup is complete. Therefore, the impact of journal backup on DFSMShsm availability and performance should be considered when planning a backup schedule. Non-intrusive journal backup can be used to reduce the impact on DFSMShsm availability and performance.

Message ARC0750I indicates which method is in use and why non-intrusive journal backup was not performed. All requirements to use non-intrusive journal backup must be satisfied.

Enabling non-intrusive journal backup

To enable and use non-intrusive journal backup, the non-intrusive journal backup requirements must be satisfied. See Requirements to use non-intrusive journal backup.

Disabling non-intrusive journal backup

There is no method of disabling non-intrusive journal backup. Non-intrusive journal backup will be used instead of quiesced journal backup as long as the non-intrusive journal backup requirements are satisfied.

Requirements to use non-intrusive journal backup

Requirements that must be satisfied to enable and use non-intrusive journal backup are:
  • The SETSYS JOURNAL(RECOVERY) setting is in effect.
    • Add the SETSYS JOURNAL(RECOVERY) command to the ARCCMDxx parmlib member of SYS1.PARMLIB and restart DFSMShsm.
    • Issue the SETSYS JOURNAL(RECOVERY) command after DFSMShsm is started.
  • The control data sets are configured to be backed up using concurrent copy.

Related reading