Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

5
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
the 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 replica database, proceed to step 6.
6
On the primary host, suspend updates to the volume that contains the
database tables. A database may have a hot backup mode that allows you to
do this by temporarily suspending writes to its tables.
7
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
This step sets up the snapshot volumes ready for the backup cycle, and starts
tracking changes to the original volumes.
8
On the primary host, if you temporarily suspended updates to a volume in
step 6, release all the database tables from hot backup mode.
9
On the primary host, deport the snapshot volume’s disk group using the
following command:
# vxdg deport snapvoldg
401Configuring off-host processing
Implemention of off-host processing solutions