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 without tags
In the first example, cloned disks (ShadowImage™ devices) from an Hitachi TagmaStore array will be imported. The primary (non-cloned) disks, mydg01, mydg02 and mydg03, are already imported, and the cloned disks are not tagged.
# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS TagmaStore-USP0_3 auto:cdsdisk - (mydg) online udid_mismatch TagmaStore-USP0_23 auto:cdsdisk mydg02 mydg online TagmaStore-USP0_25 auto:cdsdisk mydg03 mydg online TagmaStore-USP0_30 auto:cdsdisk - (mydg) online udid_mismatch TagmaStore-USP0_31 auto:cdsdisk - (mydg) online udid_mismatch TagmaStore-USP0_32 auto:cdsdisk mydg01 mydg online
To import the cloned disks, they must be assigned a new disk group name, and their UDIDs must be updated:
# vxdg -n snapdg -o useclonedev=on -o updateid import mydg # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS TagmaStore-USP0_3 auto:cdsdisk mydg03 snapdg online clone_disk TagmaStore-USP0_23 auto:cdsdisk mydg02 mydg online TagmaStore-USP0_25 auto:cdsdisk mydg03 mydg online TagmaStore-USP0_30 auto:cdsdisk mydg02 snapdg online clone_disk TagmaStore-USP0_31 auto:cdsdisk mydg01 snapdg online clone_disk TagmaStore-USP0_32 auto:cdsdisk mydg01 mydg online
Note that the state of the imported cloned disks has changed from online udid_mismatch to 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 TagmaStore-USP0_3 auto:cdsdisk - (mydg) online udid_mismatch TagmaStore-USP0_23 auto:cdsdisk - (mydg) online TagmaStore-USP0_25 auto:cdsdisk - (mydg) online TagmaStore-USP0_30 auto:cdsdisk - (mydg) online udid_mismatch TagmaStore-USP0_31 auto:cdsdisk - (mydg) online udid_mismatch TagmaStore-USP0_32 auto:cdsdisk - (mydg) online
To import only the cloned disks into the mydg disk group:
# vxdg -o useclonedev=on -o updateid import mydg # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS TagmaStore-USP0_3 auto:cdsdisk mydg03 mydg online clone_disk TagmaStore-USP0_23 auto:cdsdisk - (mydg) online TagmaStore-USP0_25 auto:cdsdisk - (mydg) online TagmaStore-USP0_30 auto:cdsdisk mydg02 mydg online clone_disk TagmaStore-USP0_31 auto:cdsdisk mydg01 mydg online clone_disk TagmaStore-USP0_32 auto:cdsdisk - (mydg) online
In the next example, a cloned disk (BCV device) from an EMC Symmetrix DMX array is to be imported. Before the cloned disk, EMC0_27
, has been split off from the disk group, the vxdisk list command shows that it is in the error udid_mismatch state:
# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_1 auto:cdsdisk EMC0_1 mydg online EMC0_27 auto - - error udid_mismatch
The symmir command is used to split off the BCV device:
# /usr/symcli/bin/symmir -g mydg split DEV001
After updating VxVM's information about the disk by running the vxdisk scandisks command, the cloned disk is in the online udid_mismatch state:
# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_1 auto:cdsdisk EMC0_1 mydg online EMC0_27 auto:cdsdisk - - online udid_mismatch
The following command imports the cloned disk into the new disk group newdg
, and updates the disk's UDID:
# vxdg -n newdg -o useclonedev=on -o updateid import mydg
The state of the cloned disk is now shown as online clone_disk:
# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS EMC0_1 auto:cdsdisk EMC0_1 mydg online EMC0_27 auto:cdsdisk EMC0_1 newdg online clone_disk