Video Screencast Help

SFHA Solutions 6.0.1: Troubleshooting VxVM and VVR

Created: 13 Sep 2012 • Updated: 14 Sep 2012
samg_writer's picture

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:

TechNote193158

The Veritas Storage Foundation and High Availability Solutions Troubleshooting Guide also includes these VxVM troubleshooting chapters:

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:

Primary SRL volume overflow recovery

The Troubleshooting Guide discusses these VVR troubleshooting topics:

Learning more

In addition to VxVM and VVR, the Troubleshooting Guide includes detailed information on detecting and correcting issues with: