Veritas InfoScale™ 8.0.2 Storage and Availability Management for Oracle Databases - AIX, Linux, Solaris

To upgrade an existing volume created with an earlier version of VxVM

1. Upgrade the disk group that contains the volume to version 120 or higher before performing the remainder of the procedure described in this section. Use the following command to check the version of a disk group:

   # vxdg list diskgroup
   						

   To upgrade a disk group to the latest version, use the following command:

   # vxdg upgrade diskgroup
   						

2. If the volume to be upgraded has a DRL plex or subdisk from an earlier version of VxVM, use the following command to remove this:

   # vxassist [-g diskgroup] remove log volume [nlog=n]
   					

   Use the optional attribute nlog=n to specify the number, n, of logs to be removed. By default, the vxassist command removes one log.

3. For a volume that has one or more associated snapshot volumes, use the following command to reattach and resynchronize each snapshot:

   # vxsnap [-g diskgroup] snapback snapvol
   						

   If persistent FastResync was enabled on the volume before the snapshot was taken, the data in the snapshot plexes is quickly resynchronized from the original volume. If persistent FastResync was not enabled, a full resynchronization is performed.

4. Use the following command to turn off persistent FastResync for the volume:

   # vxvol [-g diskgroup] set fastresync=off volume
   						

5. Use the following command to dissociate a DCO object from an earlier version of VxVM, DCO volume and snap objects from the volume:

   # vxassist [-g diskgroup] remove log volume logtype=dco
   					

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.