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

# vxplex [-g diskgroup] -o rm dis mirror
For example, to dissociate and remove a mirror named vol01-02 from the disk
group mydg, use the following command:
# vxplex -g mydg -o rm dis vol01-02
This command removes the mirror vol01-02 and all associated subdisks. This is
equivalent to entering the following commands separately:
# vxplex -g mydg dis vol01-02
# vxedit -g mydg -r rm vol01-02
Adding logs and maps to volumes
Veritas Volume Manager supports the following types of volume logs and maps:
■ FastResync Maps improve performance and reduce I/O during mirror
resynchronization. These maps can be either in memory (Non-Persistent) or
on disk (Persistent) as part of a DCO volume.
See “FastResync” on page 63.
See “Enabling FastResync on a volume” on page 373.
Two types of DCO volumes are supported:
■ Version 0 DCO volumes only support Persistent FastResync for the
traditional third-mirror break-off type of volume snapshot.
See “Version 0 DCO volume layout” on page 66.
■ Version 20 DCO volumes, introduced in VxVM 4.0, combine DRL logging
(see below) and Persistent FastResync for full-sized and space-optimized
instant volume snapshots.
See “Version 20 DCO volume layout” on page 66.
See “Preparing a volume for DRL and instant snapshots” on page 359.
■ Dirty Region Logs let you quickly recover mirrored volumes after a system
crash. These logs can be either DRL log plexes, or part of a version 20 DCO
volume.
See “Dirty region logging” on page 57.
See “Adding traditional DRL logging to a mirrored volume” on page 365.
See “Preparing a volume for DRL and instant snapshots” on page 359.
■ RAID-5 logs prevent corruption of data during recovery of RAID-5 volumes.
These logs are configured as plexes on disks other than those that are used
for the columns of the RAID-5 volume.
See “RAID-5 logging” on page 49.
Administering volumes
Adding logs and maps to volumes
358