An issue was identified in backup jobs running in incremental with commit 100f113 or release 6.5.0. If one of your incremental backup chains was corrupted, it lead to a cleaning of vdis folder resulting into backup lose.
Please update your source at least to 4552fb9 or your XOA to 6.5.1.
If you encountered issues about a warning with aliases, you are concerned. You need to run your backup jobs again to have your backups back on track.
Hi,
The latest version of XO-lite has an issue, that is why we are temporarily reverting to version 0.19.0. Sorry for the lack of communication on our part.
@itservices Hi,
We did not forget you, working on it!
@Pilow Hi,
Thank you for your reporting! It should be fixed in the next version we are thinking releasing this month if no surprise happens. There is a big refactoring on the clean part which handles metadata (and size) updates.
@Pilow Hi,
Thank you for the report.
We are fixing this in https://github.com/vatesfr/xen-orchestra/pull/9362.
It will be fixed during in a patch.
If you need to install something from hub now, you can get back to Stable branch
@MajorP93 I am currently working on this issue but to answer you quickly, yes we have automatic tests, unit and integration tests (you can see them in *.integ.mjs and *.test.mjs files, and @xen-orchestra/qatest folder), a long QA to validate at each release. We add a regression test at every bug we encounter.
The issue is we could not reproduce your exact issue yet.
@Tristis-Oris Hi,
Can you upload your complete logs from one of these jobs, please? You can DM me if you prefer 
@itservices Can you check your health dashboard where you should see " Unhealthy VDIs" ? If there are too many VDI in it, they need to be coalesced before restarting a backup.
They run once a day @ 03:04 before the normal backup that starts @ 03:10 and they have all run OK since July 8, the failed one reported 8 days ago ( post ~85 )
Hi, just to be sure, are you saying it is working ok apart one task 8 days ago?
@ph7 Hi,
Thank you for your log, can you give me the logs before the backup operation if it happens again?
Another thing to check is the exact time between your XO and your host. Maybe you should resync your clock.
I ask that because it seems XAPI was unavailable before this backup or there was a gap of 5 min between the time the backup started and XAPI actually doing this backup.
Maybe you had a xapi db sync just before this backup, do you make these backup regularly? If it is too often (every 5 min for example), it can struggle to start the backup.
@pedro_udifar Hi,
This is a b2 side error. It could be just a transient error, did you try to restart the backup?
@bogikornel @jb @gregbinsd @majorp93
We tested metadata backups every 5 min and it works in XO. It seems it might be coming from XCP-NG, can you provide us a xensource.log from the problematic timeline?
@bogikornel Can you tell us on which versions you are please?
the ones where it works and the ones where it does not work.
Thanks for your help!
@MajorP93 I am currently working on this issue but to answer you quickly, yes we have automatic tests, unit and integration tests (you can see them in *.integ.mjs and *.test.mjs files, and @xen-orchestra/qatest folder), a long QA to validate at each release. We add a regression test at every bug we encounter.
The issue is we could not reproduce your exact issue yet.
@pedro_udifar Hi,
We think we have found two issues into one: can you test this branch please? It has the changes from previous branch you built: fix_throttled_stream
This should fix the stream issue and fix the warning.
@pedro_udifar Hi, just to be sure, this is a replication job with two s3? If yes, is the source s3 encrypted or is it only the target?
@Tristis-Oris Hi,
Can you upload your complete logs from one of these jobs, please? You can DM me if you prefer
@itservices Hi, xen-bugtools is in xcp-ng hosts. You can directly get the logs from the hosts if you don't have the command.