Veritas File System 5.0 Administrator's Guide (September 2006)

# mount -F vxfs -o ckpt=may_23,remount,rw \
/dev/vx/dsk/fsvol/vol1:may_23 /fsvol_may_23
■ To mount this Storage Checkpoint automatically when the system starts up,
put the following entries in the /etc/fstab file:
Device-Special-File Mount-Point fstype options backup- pass-
frequency number
/dev/vx/dsk/fsvol/ /fsvol vxfs defaults 0 0
vol1
/dev/vx/dsk/fsvol/ /fsvol_may_23 vxfs ckpt=may_23 0 0
vol1:may_23
■ To mount a Storage Checkpoint of a cluster file system, you must also use the
–o cluster option:
# mount -F vxfs -o cluster,ckpt=may_23 \
/dev/vx/dsk/fsvol/vol1:may_23 /fsvol_may_23
You can only mount a Storage Checkpoint cluster-wide if the file system that
the Storage Checkpoint belongs to is also mounted cluster-wide. Similarly,
you can only mount a Storage Checkpoint locally if the file system that the
Storage Checkpoint belongs to is mounted locally.
You can unmount Storage Checkpoints using the command.
# umount /fsvol_may_23
# umount /dev/vx/dsk/fsvol/vol1:may_23
Note: You do not need to run the fsck utility on Storage Checkpoint pseudo devices
because pseudo devices are part of the actual file system.
Converting a data Storage Checkpoint to a nodata Storage Checkpoint
A nodata Storage Checkpoint does not contain actual file data. Instead, this type
of Storage Checkpoint contains a collection of markers indicating the location of
all the changed blocks since the Storage Checkpoint was created.
You can use either the synchronous or asynchronous method to convert a data
Storage Checkpoint to a nodata Storage Checkpoint; the asynchronous method
is the default method. In a synchronous conversion, fsckptadm waits for all files
to undergo the conversion process to “nodata” status before completing the
operation. In an asynchronous conversion, fsckptadm returns immediately and
marks the Storage Checkpoint as a nodata Storage Checkpoint even though the
Storage Checkpoints
Storage Checkpoint administration
80