Veritas Storage Foundation Intelligent Storage Provisioning 5.0.1 Administrators Guide, HP-UX 11i v3, First Edition, November 2009

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 snapvols
parent volume.
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 124.
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 121.
The following command dissociates the snapshot, snap2myvol, from its parent
volume:
# vxsnap -g mydg dis snap2myvol
When applied to a volume set or to a component volume of a volume set, this
operation can result in inconsistencies in the snapshot hierarchy in the case of a
system crash or hardware failure. If the operation is applied to a volume set, the
-f (force) option must be specified.
Removing an instant snapshot
When you have dissociated a full-sized instant snapshot, you can use the vxassist
command to delete it altogether, as shown in the following example:
# vxassist -g mydg remove volume snap2myvol
You can also use this command to remove a space-optimized instant snapshot
from its cache.
See Removing a cache on page 106.
121Administering instant snapshots
Creating instant snapshots