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
Volume status descriptions
One of the following volume status descriptions always appears in the graphical view of the volume and in the Status column of the volume in list view. If there is a problem with a volume, you can use this troubleshooting chart to diagnose and correct the problem.
Warning:
The suggested actions may bring the volumes to a Healthy status, but they do not guarantee data integrity.
Table: Volume Status Descriptions
Status | Meaning | Action Required |
---|---|---|
| The volume is accessible and has no known problems. This is the normal volume status. Both dynamic volumes and basic volumes display the Healthy status. | No user action is required. |
| The volume's mirrors are resynchronized so that both mirrors contain identical data. Both dynamic and basic mirrored volumes display the Resynching status. When resynchronization is complete, the mirrored volume's status returns to Healthy. Resynchronization may take some time, depending on the size of the mirrored volume. | No user action is required. Although you can safely access a mirrored volume while resynchronization is in progress, you should avoid making configuration changes (such as breaking a mirror) during resynchronization. |
| Data and parity are regenerated for a RAID-5 volume. Both dynamic and basic RAID-5 volumes display the Regenerating status. When regeneration is complete, the RAID-5 volume's status returns to Healthy. | No user action is required. You can safely access a RAID-5 volume while data and parity regeneration is in progress. |
| The Degraded status applies only to mirrored or RAID-5 volumes on basic or dynamic disks. There are three situations where Degraded status can occur: | Take the following actions to resolve these situations: |
Situation 1 The data on the volume may no longer be fault tolerant because one of the underlying disks is not online. A RAID-5 volume loses redundancy if one disk is offline or failed. A mirrored volume can lose redundancy if one of the disks containing one of its subdisks fails. | Situation 1 You can continue to access the volume using the remaining online disks, but you should repair the volume as soon as possible. It is important to repair the volume because if another disk that contains the volume fails, you lose the volume and its data. | |
Situation 2 A Degraded status also displays if a disk involving a RAID-5 or mirrored volume was physically moved. | Situation 2 To correct the problem, you must move all the disks that contain the volume to the new location or return the moved disk or disks to the original location. | |
Situation 3 The data on the volume is no longer fault tolerant, and I/O errors have been detected on the underlying disk. If an I/O error is detected on any part of a disk, all volumes on the disk display the (At Risk) status. Only dynamic mirrored or RAID-5 volumes display the Degraded (At Risk) status. | Situation 3 To return the underlying disk to the Online status, reactivate the disk (using the Reactivate Disk command). Once the disk is returned to the Online status, the volume status should change to Degraded. Take further action as necessary to bring the volume back to a healthy state. | |
| A failed volume starts automatically. An error icon appears on the failed volume. Both dynamic and basic volumes display the Failed status. There are two situations where Failed status can occur: | Take the following actions to resolve these situations: |
Situation 1 A volume that spans two or more disks has one or more disks fail. A striped volume, simple volume, spanned volume, or extended partition fails with one disk failure. A RAID-5 volume fails with two disk failures. A mirrored or mirrored-striped volume fails when the disks containing all the mirrors in the volume fail. | Situation 1 Replace or repair the failed or malfunctioning disk or disks. | |
Situation 2 A disk or disks involving a volume that spans multiple disks is moved to another computer. | Situation 2 Move all the disks that contain subdisks of the volume, or return the moved disk or disks to the original location. | |
| The volume is formatted using the specifications you chose for formatting. | No user action is required. |
| The volume is in a dynamic disk group that is not imported. | Import the dynamic disk group containing the volume. |
| The volume status is Missing if any of the subdisks of the volume are on the disks that show an Offline status. | Reactivate the offline disks and Rescan. If the volume status changes to Stopped or Failed, reactivate the volume. |
| Failing is a secondary message shown in parentheses after a volume status. Failing means Storage Foundation encountered some I/O errors on at least one disk that contains subdisks of the volume; however, these errors did not compromise the data on the specific volume. Failing sends the message that the disk integrity is deteriorating. When the volume status is Degraded (At Risk), the underlying disk's status is usually Online (Failing). | Determine which disk is failing, and take corrective action. |