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

To set up a replica database using the table files that are configured within a volume
in a private disk group
1
Use the following command on the primary host to see if the volume is
associated with a version 20 data change object (DCO) and DCO volume that
allow instant snapshots and Persistent FastResync to be used with the volume:
# vxprint -g volumedg -F%instant volume
This command returns on if the volume can be used for instant snapshot
operations; otherwise, it returns off.
If the volume was created under VxVM 4.0 or a later release, and it is not
associated with a new-style DCO object and DCO volume, it must be prepared.
See “Preparing a volume for DRL and instant snapshots” on page 359.
If the volume was created before release 4.0 of VxVM, and has any attached
snapshot plexes, or is associated with any snapshot volumes, it must be
upgraded.
See “Upgrading existing volumes to use version 20 DCOs” on page 366.
2
Use the following command on the primary host to check whether FastResync
is enabled on a volume:
# vxprint -g volumedg -F%fastresync volume
This command returns on if FastResync is enabled; otherwise, it returns off.
If FastResync is disabled, enable it using the following command on the
primary host:
# vxvol -g volumedg set fastresync=on volume
3
Prepare the OHP host to receive the snapshot volume that contains the copy
of the database tables. This may involve setting up private volumes to contain
any redo logs, and configuring any files that are used to initialize the database.
4
On the primary host, create a new volume in a separate disk group for use as
the snapshot volume.
For more information about snapshots, see the Veritas Storage Foundation
Advanced Features Administrator's Guide.
It is recommended that a snapshot disk group is dedicated to maintaining
only those disks that are used for off-host processing.
Configuring off-host processing
Implemention of off-host processing solutions
400