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
vxdg split
vxdg -g<SourceDynamicDiskGroupName> -n<TargetDynamicDiskGroupName>
[-i] [-f] [-s|-d] [-y] [-v] split [<Object>...]
Splits a dynamic disk group into two dynamic disk groups. The disks and volumes that are in the split-off disk group must be healthy. Also, the volumes that are in the new disk group must be complete for the command to succeed.
Microsoft Disk Management Disk Groups do not support the vxdg split command.
-g<SourceDynamicDiskGroupName> | Name of the current dynamic disk group. |
-n<TargetDynamicDiskGroupName> | Name of the new dynamic disk group. |
-i | Makes the new dynamic disk group to be in the Imported state. |
-f | Forces the split. Use this command with care. |
-s | Makes the new dynamic disk group a cluster dynamic disk group. |
-d | Changes the target disk group from a cluster disk group to a regular disk group. |
-y | Query for the split closure. See the first example below. |
-v | Splits all disks in the dynamic disk group that contain snapshot volumes. Do not use the <Object> parameter when you use this option. |
<Object> | Name of a disk or volume, or a drive letter. You can split by either disks or volumes. This option is not needed when using the -v option. The internal volume and disk name can be used. The <DrivePath> parameter is supported for a volume name. Also, a disk can be indicated by the p#c#t#l# parameter; the #s correspond to port, channel, target, and LUN. |
If you have dynamic disk groups created in an early release of Volume Manager, you need to upgrade them to be compatible with Storage Foundation for Windows dynamic disk groups before you can use the vxdg split and join commands. To do this you use the vxdg upgrade command.
By default, the new dynamic disk group is in the Deported state after the split. You can use the -i option to have it be in the Imported state. The source dynamic disk group remains in the Imported state.
With the VEA GUI split command, if the source disk group is a cluster disk group or a disk group with private dynamic disk group protection, the resulting target disk group is of the same disk group type. With a CLI split command for either of these two disk group types, you must use the -i switch. In a CLI split operation with either of these disk group types, the target disk group does not assume the disk group type of the source disk group until after the target disk group is imported.
Note:
In earlier versions of Volume Manager, it was necessary to designate the -s switch with every command involving a cluster disk group. However, in SFW, you use the -s switch only the first time you designate a cluster disk group. The -d switch has been added to allow changing a cluster disk group to an ordinary disk group.
Before using dynamic disk group split and join commands with a cluster on shared storage, you should review the considerations for doing so.
Examples
vxdg -gDynDskGrp1 -y -nDynDskGrp2 split Harddisk5 Harddisk7
This command makes a query to determine whether Harddisk5 and Harddisk7 in a dynamic disk group named "DynDskGrp1" comprise the total disks that are needed to have a dynamic disk group split where all the volumes in the split-off dynamic disk group are complete. Here is the output from the command:
Following is the Closure for the requested Splitoperation. Names of the Disks are.... Harddisk7 Harddisk5 Harddisk6 Names of the Volumes are.... \Device\HarddiskDmVolumes\DynDskGrp1\Volume1 \Device\HarddiskDmVolumes\DynDskGrp1\Stripe1
The output indicates that to have a successful split, or what is called "split closure," Harddisk6 must be added. The example of the command to perform the actual split is as follows:
vxdg -gDynDskGrp1 -i -nDynDskGrp2 split Harddisk5 Harddisk6 Harddisk7
This command results in successfully splitting the dynamic disk group DynDskGrp1 with the target dynamic disk group DynDskGrp2 in the Imported state. The new dynamic disk group has the disks Harddisk5, Harddisk6, and Harddisk7.
The example that follows designates the volumes to be included in a new target disk group. Note the path name that is needed for volumes.
vxdg -gDynDskGrp1 -i -nDynDskGrp2 split \Device\HarddiskDmVolumes\DynDskGrp1\mirrorvol1 \Device\HarddiskDmVolumes\DynDskGrp1\mirrorvol2
This command results in successfully splitting the dynamic disk group DynDskGrp1 with the target dynamic disk group DynDskGrp2 in the Imported state. The new dynamic disk group contains the volumes \Device\HarddiskDmVolumes
\DynDskGrp2\mirrorvol1 and \Device\HarddiskDmVolumes
\DynDskGrp2\mirrorvol2.
vxdg -gtest -nnew split p1c0t1l0 p1c0t2l0
This command performs the split operation. The name of the new disk group is "new." This command shows an example of the use of the p#c#t#l# with the <Object> parameter.
vxdg -gtest -nnew split Disk1 Disk2
This command performs the split operation. This example shows the use of the internal disk name with the <Object> parameter.
vxdg -gtest -nnew split Volume1 Volume2
This command performs the split operation. This example shows the use of the internal volume name with the <Object> parameter.
vxdg -gtest -nnew split L:\Folder
This command performs the split operation. This example shows the use of <DrivePath> with the <Object> parameter.
vxdg -gtest -nnew split Volume1 Volume2 -f
This command performs the split operation. This example shows the use of the -f force option.