CBT is not available for replication jobs after failback is performed.

[Asahi]

Hi ,

I have a question regarding replication in Veeam.
I ran replication against another vCenter in a VMware environment and tested the failover.

Then I selected "Failback to the original VM" and committed the failback to the original VM.
※I did not enable quick rollback.

After that, when I ran the replication job, I got the following message.
=====
2021/02/09 0:02:31 :: Cannot find dirty block information in the previous restore point, CBT will not be used
=====

This message is occurring only in the first replication job session after failback.
In subsequent replication jobs, CBT is running and detecting differential blocks without full scan.

Is it a specification that this message is output after committing the failback?

Kind Regards,
Asahi,
Climb Inc.

[HannesK]

Hello,
looks fine to me. There cannot be CBT information.

Best regards,
Hannes

[Asahi]

Hello Hannes,

Thank you for reply!
Is there something wrong with my vSphere environment?

Best Regards,
Asahi

[HannesK]

not as far as I see.

[Andreas Neufert]

Restore to original VM will keep the VM moref ID within the vCenter. For Veeam this VM is the same VM then after your restore.
For safety reasons you can not continue to use CBT information after restore and so the CBT inforamtion is resettet with the restore.

Next Job run will detect this and will perform what we call a "Snap and Scan" processing where we enable CBT again and read once all data to detect the changes. After that incremental forever processing continues to work.

[Asahi]

Hi Andreas and Hannes,

Thank you for information!
OK, I was able to understand why this message was being output.

Thank you for all your accurate and quick replies!

Best Regards,
Asahi.