Database Storage Checkpoints and rollback provides the following advantages:

• Initially, a Database Storage Checkpoint contains no data - it contains only the inode list and the block map of the primary fileset. The block map points to the actual data on the primary file system.

• Because only the inode list and block map are needed and no data is copied, creating a Database Storage Checkpoint takes only a few seconds and very little space.

• A Database Storage Checkpoint keeps track of block change information and thereby enables incremental database backup at the block level.

• A Database Storage Checkpoint helps recover data from incorrectly modified files.

• A Database Storage Checkpoint can be mounted, allowing regular file system operations to be performed. Mounted Database Storage Checkpoints can be used for a wide range of application solutions that include backup, investigations into data integrity, staging upgrades or database modifications, and data replication solutions.

The limitations of Database Storage Checkpoints are as follows:

• Database Storage Checkpoints can only be used to restore from logical errors (for example, a human error).

• Because all the data blocks are on the same physical device, Database Storage Checkpoints cannot be used to restore files due to a media failure. A media failure requires a database restore from a tape backup or a copy of the database files that are kept on a separate medium.