@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.

@itservices
Can you export your logs with xen-bugtool --yestoall please? If you prefer to avoid exporting everything, we especially need /var/log/xensource.log and /var/log/SMlog
@Team-Storage do you have an idea about the source of the issue?

@skipthompson81 Hi, as you have an XOA, can you open a support tunnel to allow us to investigate further into this issue please? You can open a ticket and ask for Pierre Brunet.

This warning is a log we added to be sure we check everything in the backups but it can be alarming indeed but the checks are hard to do and can be false positive so we don't want to panic everyone.

@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.

@itservices Hi,
We did not forget you, working on it!

@itservices It may be a storage or a xo issue. You can try to restart xo-server and retry the backup. If it is solved, it was an issue with xo-server not freeing your vdi. If it still happens, it will be a storage issue

@itservices Hi,
It seems the parent of the backup chain is not found (a delta backup links to another delta and another, until you have a full backup, it seems a backup on this chain is missing).
Can you restart a backup chain to have a full backup? You can do it by reducing the retention in your backup job.

@CGB Hi, are you running XO from source with root or another user?
If it is another user, it may be not accessible from it

@FagnerMoraes The delta backups are in vdis folder. You can see it just below cache.json.gz

@FagnerMoraes I just realized you are not listing the same folder that what is backed up in your NAS backup job: on the left, you are listing incremental backups from a given folder, but in the logs I analysed the xva are in another folder

@FagnerMoraes Is your backup encrypted?

Moreover, can you show me one metadata file that is supposed to work please?

@FagnerMoraes Hi,
Can you upload your logs please? It is a bit difficult with only screenshots. You can download them from the very modal you are in this screenshot. You can remove any personal name, I just need the logs to see where this comes from but I suspect you have two broken XVA (indeed, you have more than two json metadata).
At first glance, I would advise you to use a new folder in your NAS to be sure everything goes well

@Andrew ok, thank you. This one indeed is not supposed to be triggered indeed.

@Andrew You mean it fails the whole job for this warning? Or this is just a warning inside a successful job?

@Andrew
Your error happens after a successful merge in s3 which removes old alias not found (expected). However, the error given by s3 is not generic so it was not handled by alias checking. This issue was always there but we decided to show the warnings during backup and fix them with this new refactoring.

Can you try this branch please?
https://github.com/vatesfr/xen-orchestra/tree/pbt_fix_warning_backup

@Andrew I think I found the issue, I am working on it

@MajorP93 We are building an automated QA that we keep updating and running regularly (preferably nightly) to add any event possible. We missed this one because we did not took enough failures into account, so we added a regression test for this too.

@Andrew The warning may still appear indeed but I think it is another issue or maybe a good warning to check your backups. Can you provide the new logs please?

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.