Replica VM health warning persists after successful failback

Scenario

Replication or replica health remains in warning state even though a failback seemed to complete cleanly.

Inspect replication logs and checkpoints rather than trusting the summary banner.
Confirm the original source and target roles are fully re-established.
Check whether old recovery points are orphaned after the event.
Run a small validation cycle before declaring the protection chain healthy again.

Document what changed, what confirmed the fix, and whether the issue points to a broader standards gap worth addressing for the client.

Subjects