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
Command line log
SFW provides support for a log that captures commands that are issued through the CLI. The command line log also captures the system response to each command. The log file, vxcli.log, is typically located at C:\Program Files\Veritas\Veritas Volume Manager\logs.
Each entry in the log is prefixed with the date and time of the command or system response, followed by the process identification and thread identification. Each CLI command is a separate entry in the log and each is identified by " ---------- Command : ". Each system response is also a separate entry in the log and follows the CLI command.
Note:
Help messages are not recorded in the command line log.
As an example of a log's content, the following was recorded as a result of entering vxdg list
03/28/06 22:59:37 [5376,2024] ---------- Command : vxdglist 03/28/06 22:59:38 [5376,2024] Disk groups are.... 03/28/06 22:59:38 [5376,2024] Name : BasicGroup 03/28/06 22:59:38 [5376,2024] Disk Group Type : Basic 03/28/06 22:59:38 [5376,2024] DiskGroup ID : No ID 03/28/06 22:59:38 [5376,2024] Status : Imported 03/28/06 23:00:08 [4212,5760] ---------- Command : vxdisklist 03/28/06 23:00:09 [4212,5760] Name MediaName DiskgroupDiskStyle Size(MB) FreeSpace(MB) Status 03/28/06 23:00:09 [4212,5760] Harddisk0 BasicGroup MBR117239 67240 Uninitialized 03/28/06 23:00:09 [4212,5760] Harddisk1 BasicGroup MBR1019 917 Uninitialized 03/28/06 23:00:09 [4212,5760] Harddisk2 (No Signature)BasicGroup MBR 10236 10236 Uninitialized 03/28/06 23:00:09 [4212,5760] Harddisk3 BasicGroup MBR1019 917 Uninitialized 03/28/06 23:00:09 [4212,5760] Harddisk4 (No Signature)BasicGroup MBR 10236 10236 Uninitialized 03/28/06 23:01:41 [1100,4728] ---------- Command : vxdg-g dg1 init harddisk1 03/28/06 23:01:47 [1100,4728] Successfully createddynamic disk group dg1