Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

6
Use the following command on the volume to upgrade it:
# vxsnap [-g diskgroup] prepare volume \
alloc="disk_name1,disk_name2"
Provide two disk names to avoid overlapping the storage of the snapshot DCO
plex with any other non-moving data or DCO plexes.
The vxsnap prepare command automatically enables persistent FastResync
on the volume and on any snapshots that are generated from it. It also
associates a DCO and DCO log volume with the volume to be snapshot.
7
To view the existing DCO plexes and see whether there are enough for the
existing data plexes, enter:
# vxprint -g diskgroup
There needs to be one DCO plex for each existing data plex.
8
If there are not enough DCO plexes for the existing data plexes, create more
DCO plexes:
# vxsnap [-g diskgroup] addmir dco_volume_name [alloc=disk_name]
where dco_volume_name is the name of the DCO volume you are creating.
9
If the plex is in a SNAPDONE state, convert it to an ACTIVE state:
# vxplex [-g diskgroup] convert state=ACTIVE data_plex
10
Convert the data plexes to a SNAPDONE state and associate a DCO plex with
the data plex that will be used for snapshot operations:
# vxplex [-g diskgroup] -o dcoplex=dco_plex_name convert \
state=SNAPDONE data_plex
where dco_plex_name is the name of the DCO plex you are creating.
In this example, the volume, data_vol, is upgraded to make use of VxVM 5.0
features.
Upgrade the disk group, PRODdg:
# vxdg upgrade PRODdg
Remove the DRL plexes or subdisks, belonging to an earlier version of VxVM,
from the volume to be upgraded:
# vxassist -g PRODdg remove log data_vol logtype=drl
245Using Database FlashSnap for backup and off-host processing
Hosts and storage for Database FlashSnap