Aller au contenu principal

vmProtect 8.0.8184 replica Failover/Failback data loss

Thread needs solution

Seems that during failover/failback the source machine is just stopped and the target machine is started with no data sync, i.e. the data gathered by source machine from the last replication task run is lost.
Please, make an extra replication task run during failback/failover process. At least make an option for that.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi KDL ltd,

In the current implementation of failover/failback process the following should happen:

1) Failover is initiated from vmProtect interface and replica starts up
2) Failback is initiated from vmProtect interface while replica is running (is in failover state)
3) The replica VM is snapshotted without powering it off and the data from this snapshot is being transferred to new location (failback target)
4) When data transfer is about to finish the replica VM is turned off and a new snapshot of it is created
5) The data from this new snapshot is incrementally added to failback target

In other words the failback from powered On replica must keep sync with the failback target as close as possible. If that's not the case then you should submit a support incident, so that we can check it and advise what could be going wrong.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

It is better to have the Failover behavior for Failback too. I.e. the replica should be started completely synced with the source.