Secondary Replication Node is listed as 'failed'.For VVR on Windows Platform

book

Article ID: 100018539

calendar_today

Updated On:

Cause

The issue can occur if

a) The disks/volumes that contribute to the volumes under VVR control are in Failing/Degraded state

OR

b) There is a mismatch in the size of the replicating volumes between Primary and Secondary site

Resolution

1) To resolve the failing disk/volume issue, from VEA, clear any "failing" flags by reactivating the disks and volumes.
 
2) For the volume size mismatch issue, right click the volumes that are part of the Replicating Group and ensure that the size of the volume is exactly the same on Primary and Secondary site (Make sure to select the "Sectors" view when viewing the volume size)

3) Attempt a "Start/Resume Replication" for the RDS from the VEA->Replication Network

Note: It may be necessary to restart replication if "Resume Replication" does not help.  If this is the case, then a full synchronization will occur.
 

 

Issue/Introduction

When viewed from the Veritas Enterprise Administrator (VEA) for Windows, the Secondary RVG is listed as 'failed'.