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
Configuring CVM using ffconfigcli
This section provides information about using the CLI-based ffconfigcli utility to prepare a cluster for CVM. Using the ffconfigcli utility from CLI, you can perform the operations that are listed below.
Note:
In the following commands, you can use the optional -verbose option at the end of a command to display information about the tasks that the command performs. For example, using the -verbose option in the following command displays information about the tasks that are performed for auto-configuring a CVM: ffconfigcli -autoconfigure -verbose
Note:
In the following commands, use only the host name of the node wherever it is required. The use of IP addresses is not supported in this case.
For information about unconfiguring a CVM cluster,
Auto-configuring a CVM cluster: Run the following command to automatically set up a CVM cluster with the same name as the Microsoft failover cluster:
ffconfigcli -autoconfigure
You must use this command first if you configure a new CVM cluster.
Adding a node to a CVM cluster: Run the following command to add a node to a configured CVM cluster:
Note:
You must use this command only after you configure a CVM cluster using the ffconfigcli -autoconfigure command. Also, to successfully add a node to the CVM cluster, the node must be added to the Microsoft failover cluster first.
ffconfigcli -addnode <NodeName>
Where, <NodeName> is the name of the node that you want to add to the CVM cluster. This is a mandatory parameter.
Adding multiple nodes to a CVM cluster: Using the -addnode command, you can add only one node at a time. You can add multiple nodes by running the command multiple times in one of the following ways:
Add the nodes one-by-one to both Microsoft failover cluster and CVM.
For example: First, add node X to Microsoft failover cluster then add it to CVM, add node Y to Microsoft failover cluster first and then to CVM, and so on.
Add all the nodes to Microsoft failover cluster first and then add them one-by-one to CVM.
For example: Add nodes X, Y, and Z to Microsoft failover cluster first. Then, add the same three nodes to CVM.
However, if you use this method, CVM auto-starts only on the node added last (node Z in the example). For the other previously-added nodes, CVM needs to be restarted. For information about restarting CVM,
Note:
Alternatively, to easily add multiple nodes, you can use the GUI-based SFW Configuration Wizard for Microsoft Failover Cluster.