Veritas Volume Manager 5.0.1 Administrator's Guide, HP-UX 11i v3, First Edition, November 2009

If a volume is specified, the snapprint command displays an error message if no
FastResync maps are enabled for that volume.
Adding a version 0 DCO and DCO volume
The version 0 DCO log volume was introduced in VxVM 3.2. The version 0 layout
supports traditional (third-mirror break-off) snapshots, but not full-sized or
space-optimized instant snapshots.
See “Version 0 DCO volume layout” on page 68.
See “Version 20 DCO volume layout” on page 68.
See “Determining the DCO version number” on page 321.
To put Persistent FastResync into effect for a volume, a Data Change Object (DCO)
and DCO volume must first be associated with that volume. When you have added
a DCO object and DCO volume to a volume, you can then enable Persistent
FastResync on the volume
See “Enabling FastResync on a volume” on page 338.
Note: You need a FastResync license key to use the FastResync feature. Even if
you do not have a license, you can configure a DCO object and DCO volume so that
snap objects are associated with the original and snapshot volumes.
See “How persistent FastResync works with snapshots” on page 69.
405Administering volume snapshots
Adding a version 0 DCO and DCO volume