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
Importing cloned disks with tags
In this example, cloned disks (BCV devices) from an EMC Symmetrix DMX array will be imported. The primary (non-cloned) disks, mydg01, mydg02 and mydg03, are already imported, and the cloned disks with the tag t1 are to be imported.
# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_4 auto:cdsdisk mydg01 mydg online EMC0_6 auto:cdsdisk mydg02 mydg online EMC0_8 auto:cdsdisk - (mydg) online udid_mismatch EMC0_15 auto:cdsdisk - (mydg) online udid_mismatch EMC0_18 auto:cdsdisk mydg03 mydg online EMC0_24 auto:cdsdisk - (mydg) online udid_mismatch
The disks are tagged as follows:
# vxdisk listtag DEVICE NAME VALUE EMC0_4 t2 v2 EMC0_4 t1 v1 EMC0_6 t2 v2 EMC0_8 t1 v1 EMC0_15 t2 v2 EMC0_18 t1 v1 EMC0_24 t1 v1 EMC0_24 t2 v2
To import the cloned disks that are tagged as t1, they must be assigned a new disk group name, and their UDIDs must be updated:
# vxdg -n bcvdg -o useclonedev=on -o tag=t1 -o updateid import mydg # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_4 auto:cdsdisk mydg01 mydg online EMC0_6 auto:cdsdisk mydg02 mydg online EMC0_8 auto:cdsdisk mydg03 bcvdg online clone_disk EMC0_15 auto:cdsdisk - (mydg) online udid_mismatch EMC0_18 auto:cdsdisk mydg03 mydg online EMC0_24 auto:cdsdisk mydg01 bcvdg online clone_disk
As the cloned disk EMC0_15 is not tagged as t1, it is not imported. Note that the state of the imported cloned disks has changed from online udid_mismatch to online clone_disk.
By default, the state of imported cloned disks is shown as online clone_disk. This can be removed by using the vxdisk set command as shown here:
# vxdisk set EMC0_8 clone=off # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_4 auto:cdsdisk mydg01 mydg online EMC0_6 auto:cdsdisk mydg02 mydg online EMC0_8 auto:cdsdisk mydg03 bcvdg online EMC0_15 auto:cdsdisk - (mydg) online udid_mismatch EMC0_18 auto:cdsdisk mydg03 mydg online EMC0_24 auto:cdsdisk mydg01 bcvdg online clone_disk
In the next example, none of the disks (neither cloned nor non-cloned) have been imported:
# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_4 auto:cdsdisk - (mydg) online EMC0_6 auto:cdsdisk - (mydg) online EMC0_8 auto:cdsdisk - (mydg) online udid_mismatch EMC0_15 auto:cdsdisk - (mydg) online udid_mismatch EMC0_18 auto:cdsdisk - (mydg) online EMC0_24 auto:cdsdisk - (mydg) online udid_mismatch
To import only the cloned disks that have been tagged as t1 into the mydg disk group:
# vxdg -o useclonedev=on -o tag=t1 -o updateid import mydg # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_4 auto:cdsdisk - (mydg) online EMC0_6 auto:cdsdisk - (mydg) online EMC0_8 auto:cdsdisk mydg03 mydg online clone_disk EMC0_15 auto:cdsdisk - (mydg) online udid_mismatch EMC0_18 auto:cdsdisk - (mydg) online EMC0_24 auto:cdsdisk mydg01 mydg online clone_disk
As in the previous example, the cloned disk EMC0_15 is not tagged as t1, and so it is not imported.