On a NetBackup Flex Scale cluster with disaster recovery configuration, the replication state shows Primary-Primary on the faulted primary cluster after takeover
Consider the following scenario on a NetBackup Flex Scale cluster on which disaster recovery is configured.
The primary cluster (siteA) has faulted.
A takeover operation is performed to make siteB as the primary cluster.
The takeover operation is successful and the user continues to use siteB.
The fault at siteA is restored and siteA is brought back online.
The replication state on the primary catalog replication shows as Primary-Primary.
So, the media and storage servers on siteA remain in Error state.
(IA-40346)
Workaround:
Login to any node of siteA and elevate.
Run the following command from the shell menu:
# /opt/VRTSnas/scripts/rep/nso_replication.sh prepare secondary
This step converts the siteA as the new secondary and starts replication resync.
The replication state shows as Resync and moves to Replicating once resync has finished.
The media and storage servers will become healthy after a few minutes.