SFHA Solutions 6.0.1: Troubleshooting VxVM and VVR
This article discusses Veritas Volume Manager (VxVM) and Veritas Volume Replicator (VVR) troubleshooting issues and solutions.
VxVM: Recognizing when the state of a device has changed (HP-UX only)
When you change the state of a Business Continuance Volume (BCV) or Symantec remote data facility device (SRDF) from write-disabled to write-enabled, VxVM does not recognize the change. The devices are in an error state, and HP-UX indicates the device paths have failed.
For detailed analysis of this issue, advice on a tunable setting, and a corrective procedure, see:
The Veritas Storage Foundation and High Availability Solutions Troubleshooting Guide also includes these VxVM troubleshooting chapters:
- Recovering from hardware failure
- Recovering from instant snapshot failure
- Recovering from boot disk failure
- Managing commands and transactions
- Backing up and restoring disk group configurations
- Troubleshooting issues with importing disk groups
- Recovering from CDS errors
- Error messages
VVR: Recovering from Primary SRL volume overflow (all platforms)
A replication link (RLINK) is STALE when the Secondary data volumes do not contain the Primary's data and cannot be brought up-to-date using the Primary Storage Replicator Log (SRL).
This issue can occur when the SRL overflows. Learn how to correct this issue and prevent future overflows see:
The Troubleshooting Guide discusses these VVR troubleshooting topics:
- Recovery from RLINK connect problems
- Recovery from configuration errors
- Recovery on the primary or secondary
In addition to VxVM and VVR, the Troubleshooting Guide includes detailed information on detecting and correcting issues with: