Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)
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
237Creating and administering disk groups
Handling cloned disks with duplicated identifiers