Symptom
A check on replication status using "vradmin repstatus" command shows "Primary-Primary configuration" under section titled "Config Errors"
Replication link (Rlink) is connected but no data flow observed
Failback synchronization is in progress but appears hung
Fact
The VVR primary system fails or stops responding.
Due to this, a VVR secondary system gets promoted to primary role using the "vradmin takeover" command, with or without the use of Auto Failback option (autofb) but with failback logging enabled (the default option).
When the original failed primary system becomes available, it automatically gets converted to a secondary system if autofb option was used. Otherwise, a "vradmin fbsync" command is issued to convert the original primary system to a secondary.
The data volumes in the Replicated Volume Group (RVG) on the original failed primary are in use.
Cause
Data volumes are in use (in open state) on VVR secondary systems.
If the data volumes contain file systems, then the file systems may be mounted.
Details
If the data volumes on the acting secondary (original primary) are in open state due to file systems in the data volumes being mounted, then these need to be un-mounted.
Un-mount all file systems that belong to volumes in the RVG.
Once all such volumes are un-mounted, failback synchronization will commence and data flow on the Rlink will be observed.
