bug about provoked BACKUP FELL BACK TO A FULL due to DR job
-
Hi,
latest XOA 6.0.3I found a case where I can provoke the

I do not understand why it happens, but it is happening anyway.We have a normal DELTA backup job with 6 VMs in it. say VM1 to VM6.
This job has advanced options of NBD+CBT checked. NBD network exists to do the backup.
Normal snapshot mode. Merge Synchronously in advanced is checked.Another job : CONTINUOUS REPLICATION, same 6 VMs, same advanced options checked
and a last job : DISASTER RECOVERY of a subset of two VMs : VM4 and VM6
ZSTD compression, normal snapshot mode, merge backup synchronously. 1 point retention (a full is done each time, as intended)All 3 jobs are in sequence, they do not overlap. first backup, second replica, third DR.
All 3 jobs execute with success, but in the BACKUP and REPLICA jobs :
only VM4 and VM6 have
with "delta" backup type at the end.the fact that the DR job is done one these two VMs provoke this behavior. this is not wanted.
What we see in REPLICA job log :

And in backup JOB log :

I checked on VM VDI after the DR job is finished and CBT is still checked

Why does a DR job resets something that make other two jobs fall back to full on these VDIs ?
-
Thanks @Pilow for the report, I'll try to reproduce on my side to get a better undertanding of what's creates the fallback.
-
@Bastien-Nollet nice.
I can confirm with the dates of the backup logs that it is since the exact date of beginning of DR job that this problem appears on the two other jobs.
when not doing NBD+CBT, the backup & replica jobs keep the "full" snapshot on the VM.
DR do not do that, it delete the snapshot.I guess this is a silent failure of the way DR manages its snapshot deletion that could delete the CBT bitmap ? and then, baaam fall back to full on other jobs relying on said bitmap... ?
this is a run of the DR job

no notion of NBD/CBT in DR job advanced parameters, it treats that differently

-
I am summoning @storage (especially G. R. )