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
Using Dynamic Disk Group Split and Join with VCS or Microsoft Failover Clustering
If a disk group is under Cluster Server (VCS) or Microsoft Failover Clustering control, SFW imposes certain conditions on the functioning of the Dynamic Disk Group Split and Join operations.
These conditions are the following:
If a shared dynamic cluster disk group is joined to another (possibly shared) dynamic disk group and the source disk group is configured as a VCS or Microsoft Failover Clustering resource, then the join operation fails.
If a dynamic disk group (possibly shared) is joined to another shared cluster dynamic disk group and the target disk group is configured as a VCS or Microsoft Failover Clustering resource, then the join operation is allowed to proceed.
(VCS only) If a shared dynamic cluster disk group is split into another (possibly shared) disk group and the source disk group is configured as a VCS resource, then the split operation is not allowed to proceed, with one exception. The exception is that the split operation can proceed when the volumes selected to be split off are not configured under VCS.
Thus, in this situation, if users want to split any volumes that are configured under VCS, they should remove the volumes from VCS monitoring and retry the split operation.
(Microsoft Failover Clustering only) If a shared dynamic cluster disk group is split into another (possibly shared) disk group and the source disk group is configured as a Microsoft Failover Clustering resource, the split operation is allowed to proceed. However, before the command completes, a confirmation window appears to remind you that if you split a disk group resource so that a volume on which other cluster resources depend is moved to a new SFW cluster disk group, it is necessary to define the new cluster disk group as a Microsoft Failover Clustering resource and to modify the properties of dependent resources to reflect the change.
If necessary, use Windows Server's Failover Cluster Manager to check and modify resource dependency fields as follows:
Define the new cluster disk group as a Volume Manager cluster disk group resource.
Even though the name of the program has changed to Storage Foundation, the resource group is still named "Volume Manager."
If the new disk group resource is in a different Microsoft Failover Cluster group than the original cluster disk group resource, move all resources that depend on the new cluster disk group resource to the Microsoft Failover Cluster group where it resides.
For each dependent resource, do the following:
Offline the resource.
Select the resource and select
.Select Dependencies in the resource's Properties window.
If the resource lists the disk group that was the source of the split operation as a dependency, click
.Move the new disk group from the Available Resources pane of the Modify Dependencies window to the Dependencies pane, and move the old disk group from the Dependencies pane to the Available Resources pane, if it appears in the Dependencies pane.
Online the resource.
(VCS only) If there is a hardware failure or a power failure during an ongoing disk group split operation and the disk group being split is configured under VCS, then VCS attempts to failover that disk group to another node in the cluster and brings the disk group online.
At that time, appropriate disk group split recovery is carried out as required to bring the disk group online.
Manual intervention may or may not be required to recover the disk group.
If you are splitting a dynamic cluster disk group that contains the quorum volume, make sure that the quorum volume is not part of the target disk group after the split operation. If you fail to do so, the quorum volume is not able to function and the cluster fails.
More Information