Replica in failover state again after commiting failback?!

[t_ahrens]

Hi all,

we did some tests last weekend, to see if our infrastructure behaves like designed in case of desaster (main datacenter is offline).
After shutting down the main datacenter, we performed failover to the replicas at the backup datacenter and tested all services for some time, then we performed failback.

Everything went fine, except one thing:
After the replica VMs were shut down and the productive VMs at the main datacenter were running stable for some time, we committed failback to the replicas.
That worked without errors, and everything was running stable like before the tests, even replication from main to backup datacenter was working again.

But now two of the replica VMs are "active" again at the backup site, the status of the VMs is "failover", although the VMs are running at the productive site and NOT powered on at the backup site.
When we try to perform failover again, it doesn't work, the error message is "replica not in failover state".

The problem is, that replication ist not working at the moment, the error message after the replication attempt is "replica IS in failover state". That doesn't make any sense to us!
It would be no problem to delete the replicas and create them again. But it isn't even possible to delete the replicas in the current condition.

We have no idea, how this might have happened. Maybe it is an issue of the vCenter Server, which was shutdown and then manually started at the backup site during the test, and afterwards shutdown at the backup site and booted up again at the main site?

How can we tell the veeam server at the backup site, that the replicas are NOT in failover state, and get them back to replicate with the running VMs at the main side again?

Thanks in advance, and best regards!
Thorger

[foggy]

Hi Thorger, I'd recommend contacting Veeam technical support for a quick assistance with this. Btw, have you tried to rescan the infrastructure in Veeam B&R?

[alex1992]

Did you solve this issue? I got same problem after upgrade to V12