Open topic with navigation
This backup method backs up data in increments, where after the first full backup, not all the data is copied during the backup, but instead just the data changes since the previous incremental backup. When starting to use incremental backup with a database, the first backup must be a full backup (the baseline) and subsequent backups are incremental backups that backup only the data changes that occurred since the last backup. This method reduces backup duration as well as the size of the backup since each backup set only includes one full copy. This allows customers with larger databases to take more frequent backups that are space efficient.
Point-in-time recovery refers to the ability to restore a data set to given point-in-time based on the incremental restore points created. The restore process will re-constitute an Archive from the Backup Set with the correct database state for a given point-in-time. A Storage Manager (SM) can be started on the restored archive.
As described above, the Backup Set must begin with a full database copy. The full copy contains the archive, journal, and fingerprints (i.e., change tracking of atoms).
After a full copy has been completed the user can run journal hot copies to capture the changes from the last hot copy - full, incremental, or a journal.
When restoring data using Incremental Hot Copy, seeking changes in the journal is being avoided since this type of backup also contains the archives themselves resulting in faster restore time.