BACKUP SYSTEM

The online BACKUP SYSTEM utility invokes z/OS® DFSMShsm (Version 1 Release 7 or above) to copy the volumes on which the DB2® data and log information resides. These system-level backups can be taken for either a DB2 subsystem or data sharing group. You can later run the RESTORE SYSTEM utility to recover the subsystem or data sharing group.

You can use BACKUP SYSTEM to copy all data for a single application (for example, when DB2 is the database server for a resource planning solution).

Restrictions:
  • All data sets that you want to copy must be SMS-managed data sets.
  • A data sharing environment, no failed abnormally quiesced members can exist. Otherwise, the BACKUP SYSTEM request fails.
  • If you want to manage the dumping of system-level backups to tape, you need to have z/OS DFSMShsm V1R8 or above.

The BACKUP SYSTEM utility uses copy pools. You must define these copy pools before you run BACKUP SYSTEM. See Copy pools.

Output

The output for BACKUP SYSTEM is the copy of the volumes on which the DB2 data and log information resides. The copies are called system-level backups.

The BACKUP SYSTEM history is recorded in the bootstrap data sets (BSDSs).

Start of changeBACKUP SYSTEM does not reset COPY-pending status. To remove COPY-pending status, take an image copy of the affected object.End of change

Related information:

Authorization required

To execute this utility, you must use a privilege set that includes SYSCTRL or SYSADM authority.

Execution phases of BACKUP SYSTEM

The BACKUP SYSTEM utility operates in these phases:
Phase
Description
UTILINIT
Performs initialization and setup.
COPY
Copies data.
UTILTERM
Performs cleanup.