Veritas Storage Foundation Intelligent Storage Provisioning 5.0.1 Administrators Guide, HP-UX 11i v3, First Edition, November 2009
result of the operation. A space-optimized instant snapshot always remains
intact at the end of the operation.
See “Restoring a volume from an instant snapshot” on page 120.
■ Dissociate the snapshot volume entirely from the original volume. This may
be useful if you want to use the copy for other purposes such as testing or
report generation. If desired, you can delete the dissociated volume.
See “Dissociating an instant snapshot” on page 121.
■ If the snapshot is part of a snapshot hierarchy, you can also choose to split
this hierarchy from its parent volumes.
See “Splitting an instant snapshot hierarchy” on page 122.
Creating and managing linked break-off snapshot volumes
Linked break-off snapshots are the only form of volume snapshot that can be used
to implement offhost processing for ISP volumes as described in the Veritas
Storage Foundation Intelligent Storage Provisioning Solutions Guide. They are also
the most suitable type of snapshot to use with write-intensive volumes, such as
database redo logs.
For linked break-off snapshots, you must prepare a volume that is to be used as
the snapshot volume. This must be the same size as the volume for which the
snapshot is being created, and it must also have the same region size.
See “Creating a volume for use as a full-sized instant or linked break-off snapshot”
on page 100.
The attributes for a snapshot are specified as a tuple to the vxsnap make command.
This command accepts multiple tuples; one for each snapshot that is being created.
Each element of a tuple is separated from the next by a slash character (/). Tuples
are separated by white space.
Administering instant snapshots
Creating instant snapshots
114