Permanent Failover Hyper-V

[tom8]

Hello guys,

i have a question regarding this specific point.

https://helpcenter.veeam.com/docs/backu ... ml?ver=110

To protect the VM replica from corruption after permanent failover is complete, Veeam Backup & Replication reconfigures the replication job: adds the VM replica in the list of processed VMs and adds the original VM to the list of exclusions. When the replication job starts, the original VM is skipped from processing. As a result, no data is written to the working VM replica.

What does this exactly mean?

[foggy]

It means that from the moment of a failover, other jobs will backup/replicate the replica VM instead of the original one.

[tom8]

Ok, thats what i intentionally thought too, but it didn´t work for me, so i asked.
Wierd.

I tried both scenarios:

Scenario 1:
HyperV1 replicates to HyperV2 --> Failover to Replica --> Permanent Failover to Replica

The original VM will get excluded but the Replica VM will not be put into the processing list.


Scenario 2:
HyperV 1 replicates to itself --> Failover to Replica --> permanent Failover to Replica

The original VM will get excluded but the Replica VM will not be put into the processing list.


What am i doing wrong or don´t see?

[foggy]

Doesn't look expected, we will check the behavior internally. Thanks for the heads up!

[foggy]

We've checked internally and it looks like documentation is somewhat confusing here as, unlike failback commit operation, Veeam B&R doesn't update any existing jobs upon a permanent failover. We will update the documentation accordingly. Thanks again for the notice.

[tom8]

Thanks for your response and quick check!