After creating a Storage Checkpoint and before using it to back up or restore a database, you can verify that the Storage Checkpoint is free of errors.
The following are usage notes for verifying a Storage Checkpoint:
To verify that a Storage Checkpoint is error-free using the command line
Create and mount a Storage Checkpoint:
$ /opt/VRTS/bin/db2ed_ckptcreate -I db2inst -D PROD -o online
Storage Checkpoint Checkpoint_903937870 created.
$ mkdir /tmp/ckpt_ro
$ /opt/VRTS/bin/db2ed_ckptmount -I db2inst -D PROD \ -c Checkpoint_903937870 -m /tmp/ckpt_ro
If the specified mount point directory does not exist, then db2ed_ckptmount creates it before mounting the Storage Checkpoint, as long as the DB2 instance owner has permission to create it.
Examine the contents of the Storage Checkpoint:
$ ls -l /tmp/ckpt_ro/db2vol_82/db2inst1 drwxr-xr-x 3 db2inst1 dba 1024 Nov 11 2000 . drwxr-xr-x 3 db2inst1 dba 512 Nov 16 11:00 .. -rw-r--r-- 1 db2inst1 dba 209747968 Nov 16 10:58 .tstmp -rw-r--r-- 1 db2inst1 dba 209747968 Nov 16 10:58 .tstab lrwxrwxrwx 1 db2inst1 dba 18 Nov 11 2000 tstmp -> .tstmp::cdev:vxfs: lrwxrwxrwx 1 db2inst1 dba 18 Nov 11 2000 tstab -> .tstab::cdev:vxfs:
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, 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 kept on a separate medium. The combination of data redundancy (disk mirroring) and Storage Checkpoints is recommended for highly critical data to protect them from both physical media failure and logical errors.