Storage Foundation 8.0 Administrator's Guide - Windows
- Overview
- Setup and configuration
- Function overview
- About the client console for Storage Foundation
- Recommendations for caching-enabled disks
- Configure basic disks (Optional)
- About creating dynamic disk groups
- About creating dynamic volumes
- Set desired preferences
- Using the GUI to manage your storage
- Working with disks, partitions, and volumes
- Adding storage
- Disk tasks
- Remove a disk from the computer
- Veritas Disk ID (VDID)
- General Partition/Volume tasks
- Mount a volume at an empty folder (Drive path)
- Expand a dynamic volume
- Shrink a dynamic volume
- Basic disk and volume tasks
- Automatic discovery of SSD devices and manual classification as SSD
- Volume Manager space allocation is SSD aware
- Dealing with disk groups
- Disk groups overview
- Delete a dynamic disk group
- Detaching and attaching dynamic disks
- Importing and deporting dynamic disk groups
- Partitioned shared storage with private dynamic disk group protection
- Fast failover in clustered environments
- iSCSI SAN support
- Settings for monitoring objects
- Event monitoring and notification
- Event notification
- Configuring Automatic volume growth
- Standard features for adding fault tolerance
- Performance tuning
- FlashSnap
- FlashSnap components
- FastResync
- Snapshot commands
- Dynamic Disk Group Split and Join
- Dynamic disk group join
- Using Dynamic Disk Group Split and Join with a cluster on shared storage
- Dynamic Disk Group Split and Join troubleshooting tips
- Fast File Resync
- Volume Shadow Copy Service (VSS)
- Using the VSS snapshot wizards with Microsoft Exchange
- Using the VSS snapshot wizards with Enterprise Vault
- Using the VSS snapshot wizards with Microsoft SQL
- Copy on Write (COW)
- Using the VSS COW snapshot wizards with Microsoft Exchange
- Using the VSS COW snapshot wizards with Microsoft SQL
- Configuring data caching with SmartIO
- Typical deployment scenarios
- About cache area
- Configuring SmartIO
- Frequently asked questions about SmartIO
- Dynamic Multi-Pathing
- Configuring Cluster Volume Manager (CVM)
- Configuring a CVM cluster
- Administering CVM
- Access modes for cluster-shared volumes
- Storage disconnectivity and CVM disk detach policy
- Unconfiguring a CVM cluster
- Command shipping
- About I/O Fencing
- Administering site-aware allocation for campus clusters
- SFW for Hyper-V virtual machines
- Introduction to Storage Foundation solutions for Hyper-V environments
- Live migration support for SFW dynamic disk group
- Preparing the host machines
- Configuring the SFW storage
- Administering storage migration for SFW and Hyper-V virtual machine volumes
- Optional Storage Foundation features for Hyper-V environments
- Microsoft Failover Clustering support
- Configuring a quorum in a Microsoft Failover Cluster
- Implementing disaster recovery with Volume Replicator
- Troubleshooting and recovery
- Using disk and volume status information
- Resolving common problem situations
- Commands or procedures used in troubleshooting and recovery
- Rescan command
- Repair volume command for dynamic mirrored volumes
- Additional troubleshooting issues
- Disk issues
- Volume issues
- Disk group issues
- Connection issues
- Issues related to boot or restart
- Cluster issues
- Dynamic Multi-Pathing issues
- vxsnap issues
- Other issues
- CVM issues
- Appendix A. Command line interface
- Overview of the command line interface
- vxclustadm
- vxvol
- vxdg
- vxclus
- vxdisk
- vxassist
- vxassist (Windows-specific)
- vxsd
- vxedit
- vxdmpadm
- vxcbr
- vxsnap
- vxscrub
- sfcache
- Tuning SFW
- Appendix B. VDID details for arrays
Importing a cloned disk group
Advanced disk arrays provide methods to create clones or copies of physical volumes (disks or LUNs) from the hardware-side. Using the hardware cloning technology, you can create a hardware snapshot (such as an EMC BCV™ or Hitachi ShadowImage™), a hardware mirror, or a hardware clone.
If a disk that you plan to clone is under SFW control, the data that is stored in the private region of the disk is also copied. As a result, the disk id in the private region of the original disk and the cloned disk remains same. Also, the VxVM disk group becomes a duplicate of the original disk group.
In order to identify a cloned disk, a unique and persistent attribute called the Veritas Device Identifier (VDID) is added to the private region of every disk. For a disk in which the original VDID differs from the one in the private region, a vdid_mismatch flag or a "shadow" flag is added to the private region. Such a disk is considered as a cloned disk.
Now, if standard (non-cloned) disks in a disk group are already imported, you cannot simultaneously import the cloned disks in the same disk group. VxVM does not support a disk group with both clone and non-clone disks. If you want to import the cloned disks, you must specify a new disk group name for the disk group containing the cloned disks. During the import process, the vdid_mismatch flag and the shadow flag are cleared from the disks in the new disk group. The new disk group becomes a standard disk group, and the disks become the standard disks.
To import the cloned disk group as a new disk group, on the same host, run the following command:
Vxdg -g SourceDGName -n NewDGName clone DiskName
Where,
SourceDGName= Name of the original disk group
NewDGName= Name of the new (cloned) disk group
DiskName= Cloned disk name
Notes:
The functionality to import a cloned disk group is disabled by default. To enable the functionality, you must set the SupportVDIDTOC registry key value to 1, and then restart the vxsvc service.
The SupportVDIDTOC registry key is located under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vxboot\VDID.
Currently, you cannot import a cloned disk group if your disk groups contains volume layout type Mirrored with Stripped.
If the process to import a cloned disk group fails or if you intend to import a cloned disk group on a new host, you must first update the VDID in the private region and then import the disk group.
You can update the VDID in any of the following ways:
Method 1:
1. Run the vxdg -gDGName updatevdid command.
Where the DGName is the name of the disk group for which the cloning process failed.
2. Run the vxdg - gDGName import command.
Method 2:
Run a clean import command vxdg -gDGName import - clean.