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

To back up a volume in a private disk group
1
On the primary host, create a new volume, snapvol, in a separate disk group,
snapvoldg, for use as the snapshot volume. This volume must be the same
size as the original volume, but it can differ in its layout and other
characteristics, such as the quality of storage. It is recommended that the
snapshot disk group contains storage that is dedicated to off-host processing.
2
On the primary host, link the snapshot volume in the snapshot disk group to
the data volume:
# vxsnap -g volumedg -b addmir volume mirvol=snapvol \
mirdg=snapvoldg
You can use the vxsnap snapwait command to wait for synchronization of
a linked snapshot volume to complete:
# vxsnap -g volumedg snapwait volume mirvol=snapvol \
mirdg=snapvoldg
This step sets up the snapshot volumes, and starts tracking changes to the
original volumes.
When you are ready to create a backup, proceed to step 3.
3
On the primary host, suspend updates to the volume that contains the
database tables. The database may have a hot backup mode that allows you
to do this by temporarily suspending writes to its tables.
4
Create the snapshot volume, snapvol, by running the following command on
the primary host:
# vxsnap -g volumedg make \
source=volume/snapvol=snapvol/snapdg=snapvoldg
If a database spans more than one volume, you can specify all the volumes
and their snapshot volumes using one command, as shown in this example:
# vxsnap -g dbasedg make \
source=vol1/snapvol=snapvol1/snapdg=sdg \
source=vol2/snapvol=snapvol2/snapdg=sdg \
source=vol3/snapvol=snapvol3/snapdg=sdg
5
On the primary host, if you temporarily suspended updates to the volume by
a database in step 3, release all the tables from hot backup mode.
35Off-host processing solutions
Implementing off-host processing solutions