Backing up and recovering your data
Db2 supports recovering data to its current state or to an earlier state. You can recover table spaces, indexes, index spaces, partitions, data sets, and the entire system. Developing backup and recovery procedures at your site is critical in order to avoid costly and time-consuming loss of data.
About this task
Develop procedures for the following recovery actions:
- Create a point of consistency
- Recovering system and data objects to a point of consistency
- Back up the Db2 catalog and directory and your data
- Recover the Db2 catalog and directory and your data
- Recover from out-of-space conditions
- Recover from a hardware or power failure
- Recover from a z/OS component failure
- Recover from a disaster off-site
Recommendation: To improve recovery capability in the event of a disk
failure, use dual active logging, and place the copies of the active log data sets and the bootstrap
data sets on different disk volumes.
Tip: For best results, check the consistency of the Db2 catalog and directory regularly, even outside of
the migration process. For detailed instructions, see Migration step 2: Verify the integrity of Db2 table spaces (optional) and Migration step 3: Check for consistency between catalog tables (optional)
The following utilities are the principal tools for Db2 recovery:
- QUIESCE
- REPORT
- COPY
- COPYTOCOPY
- RECOVER
- MERGECOPY
- BACKUP SYSTEM
- RESTORE SYSTEM
This information provides an overview of these utilities to help you with your backup and recovery planning. Note that the term page set in this information can refer to a table space, index space, or any combination of these.