Veritas™ Volume Manager Administrator's Guide
- Understanding Veritas Volume Manager
- VxVM and the operating system
- How VxVM handles storage management
- Volume layouts in VxVM
- Online relayout
- Volume resynchronization
- Dirty region logging
- Volume snapshots
- FastResync
- Provisioning new usable storage
- Administering disks
- Disk devices
- Discovering and configuring newly added disk devices
- Discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Changing the disk-naming scheme
- Adding a disk to VxVM
- Rootability
- Displaying disk information
- Removing disks
- Removing and replacing disks
- Administering Dynamic Multi-Pathing
- How DMP works
- Administering DMP using vxdmpadm
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Online dynamic reconfiguration
- Reconfiguring a LUN online that is under DMP control
- Creating and administering disk groups
- About disk groups
- Displaying disk group information
- Creating a disk group
- Importing a disk group
- Moving disk groups between systems
- Handling cloned disks with duplicated identifiers
- Handling conflicting configuration copies
- Reorganizing the contents of disk groups
- Destroying a disk group
- Creating and administering subdisks and plexes
- Displaying plex information
- Reattaching plexes
- Creating volumes
- Types of volume layouts
- Creating a volume
- Using vxassist
- Creating a volume on specific disks
- Creating a mirrored volume
- Creating a striped volume
- Creating a volume using vxmake
- Initializing and starting a volume
- Using rules and persistent attributes to make volume allocation more efficient
- Administering volumes
- Displaying volume information
- Monitoring and controlling tasks
- Reclamation of storage on thin reclamation arrays
- Stopping a volume
- Resizing a volume
- Adding a mirror to a volume
- Preparing a volume for DRL and instant snapshots
- Adding traditional DRL logging to a mirrored volume
- Enabling FastResync on a volume
- Performing online relayout
- Adding a RAID-5 log
- Creating and administering volume sets
- Configuring off-host processing
- Administering hot-relocation
- How hot-relocation works
- Moving relocated subdisks
- Administering cluster functionality (CVM)
- Overview of clustering
- Multiple host failover configurations
- CVM initialization and configuration
- Dirty region logging in cluster environments
- Administering VxVM in cluster environments
- Changing the CVM master manually
- Importing disk groups as shared
- Administering sites and remote mirrors
- About sites and remote mirrors
- Fire drill - testing the configuration
- Changing the site name
- Administering the Remote Mirror configuration
- Failure and recovery scenarios
- Performance monitoring and tuning
- Appendix A. Using Veritas Volume Manager commands
- Appendix B. Configuring Veritas Volume Manager
Moving objects between disk groups
To move a self-contained set of VxVM objects from an imported source disk group to an imported target disk group, use the following command:
# vxdg [-o expand] [-o override|verify] move sourcedg targetdg \ object ...
The -o expand option ensures that the objects that are actually moved include all other disks containing subdisks that are associated with the specified objects or with objects that they contain.
The default behavior of vxdg when moving licensed disks in an EMC array is to perform an EMC disk compatibility check for each disk involved in the move. If the compatibility checks succeed, the move takes place. vxdg then checks again to ensure that the configuration has not changed since it performed the compatibility check. If the configuration has changed, vxdg attempts to perform the entire move again.
Note:
You should only use the -o override and -o verify options if you are using an EMC array with a valid timefinder license. If you specify one of these options and do not meet the array and license requirements, a warning message is displayed and the operation is ignored.
The -o override option enables the move to take place without any EMC checking.
The -o verify option returns the access names of the disks that would be moved but does not perform the move.
The following output from vxprint shows the contents of disk groups rootdg and mydg.
The output includes two utility fields, TUTIL0 and PUTIL0.. VxVM creates these fields to manage objects and communications between different commands and Symantec products. The TUTIL0 values are temporary; they are not maintained on reboot. The PUTIL0 values are persistent; they are maintained on reboot.
# vxprint Disk group: rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg rootdg rootdg - - - - - - dm rootdg02 c1t97d0 - 17678493 - - - - dm rootdg03 c1t112d0 - 17678493 - - - - dm rootdg04 c1t114d0 - 17678493 - - - - dm rootdg06 c1t98d0 - 17678493 - - - - Disk group: mydg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg mydg mydg - - - - - - dm mydg01 c0t1d0 - 17678493 - - - - dm mydg05 c1t96d0 - 17678493 - - - - dm mydg07 c1t99d0 - 17678493 - - - - dm mydg08 c1t100d0 - 17678493 - - - - v vol1 fsgen ENABLED 2048 - ACTIVE - - pl vol1-01 vol1 ENABLED 3591 - ACTIVE - - sd mydg01-01 vol1-01 ENABLED 3591 0 - - - pl vol1-02 vol1 ENABLED 3591 - ACTIVE - - sd mydg05-01 vol1-02 ENABLED 3591 0 - - -
The following command moves the self-contained set of objects implied by specifying disk mydg01 from disk group mydg to rootdg:
# vxdg -o expand move mydg rootdg mydg01
By default, VxVM automatically recovers and starts the volumes following a disk group move. If you have turned off the automatic recovery feature, volumes are disabled after a move. Use the following commands to recover and restart the volumes in the target disk group:
# vxrecover -g targetdg -m [volume ...] # vxvol -g targetdg startall
The output from vxprint after the move shows that not only mydg01 but also volume vol1 and mydg05 have moved to rootdg, leaving only mydg07 and mydg08 in disk group mydg:
# vxprint Disk group: rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg rootdg rootdg - - - - - - dm mydg01 c0t1d0 - 17678493 - - - - dm rootdg02 c1t97d0 - 17678493 - - - - dm rootdg03 c1t112d0 - 17678493 - - - - dm rootdg04 c1t114d0 - 17678493 - - - - dm mydg05 c1t96d0 - 17678493 - - - - dm rootdg06 c1t98d0 - 17678493 - - - - v vol1 fsgen ENABLED 2048 - ACTIVE - - pl vol1-01 vol1 ENABLED 3591 - ACTIVE - - sd mydg01-01 vol1-01 ENABLED 3591 0 - - - pl vol1-02 vol1 ENABLED 3591 - ACTIVE - - sd mydg05-01 vol1-02 ENABLED 3591 0 - - - Disk group: mydg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg mydg mydg - - - - - - dm mydg07 c1t99d0 - 17678493 - - - - dm mydg08 c1t100d0 - 17678493 - - - -
The following commands would also achieve the same result:
# vxdg move mydg rootdg mydg01 mydg05 # vxdg move mydg rootdg vol1