Veritas Storage Foundation Intelligent Storage Provisioning 5.0 AdministratorÆs Guide, HP-UX 11i v3, First Edition, May 2008

114 Administering instant snapshots
Creating instant snapshots
Note: For this operation to succeed, the volume that is being restored and the
snapshot volume must not be open to any application. For example, any file
systems that are configured on either volume must first be unmounted.
It is not possible to restore a volume from an unrelated volume.
The destroy and nmirror attributes are not supported for space-optimized
instant snapshots.
The following example demonstrates how to restore the volume, myvol, from
the space-optimized snapshot, snap3myvol.
# vxsnap -g mydg restore myvol source=snap3myvol
Dissociating an instant snapshot
The following command breaks the association between a snapshot volume,
snapvol, and its parent volume, so that the snapshot may be used as an
independent volume:
# vxsnap [-f] [-g diskgroup ] dis snapvol
This operation fails if the snapshot, snapvol, has a snapshot hierarchy below it
that contains unsynchronized snapshots. If this happens, the dependent
snapshots must be fully synchronized from snapvol. When no dependent
snapshots remain, snapvol may be dissociated. The snapshot hierarchy is then
adopted by snapvol’s parent volume.
Note: To be usable after dissociation, the snapshot volume and any snapshots in
the hierarchy must have been fully synchronized.
See “Controlling instant snapshot synchronization” on page 118.
In addition, you cannot dissociate a snapshot if synchronization of any of the
dependent snapshots in the hierarchy is incomplete. If an incomplete snapshot
is dissociated, it is unusable and should be deleted.
See “Removing an instant snapshot” on page 115.
The following command dissociates the snapshot, snap2myvol, from its parent
volume:
# vxsnap -g mydg dis snap2myvol