XO error/warning: Clean VM directory. unhandled error while checking alias.

[pierrebrunet]

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

[pierrebrunet]

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

[pierrebrunet]

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

@pierrebrunet The error happens using Wasabi and MinIO. The pbt_fix_warning_backup still has the error (but no 404 error):

Clean VM directory 
 missing target of alias

Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.571Z xo:backups:MixinBackupWriter INFO Disk chain needs merging { count: 1 }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.571Z xo:backups:MixinBackupWriter INFO merging disk chain {
Jun 01 11:23:22 xo2 xo-server[4216]:   chain: [
Jun 01 11:23:22 xo2 xo-server[4216]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152042Z.alias.vhd',
Jun 01 11:23:22 xo2 xo-server[4216]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152256Z.alias.vhd'
Jun 01 11:23:22 xo2 xo-server[4216]:   ]
Jun 01 11:23:22 xo2 xo-server[4216]: }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.741Z xo:backups:MixinBackupWriter WARN missing target of alias {
Jun 01 11:23:22 xo2 xo-server[4216]:   alias: '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152042Z.alias.vhd'
Jun 01 11:23:22 xo2 xo-server[4216]: }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.741Z xo:backups:MixinBackupWriter INFO removing alias with missing target {
Jun 01 11:23:22 xo2 xo-server[4216]:   alias: '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152042Z.alias.vhd'
Jun 01 11:23:22 xo2 xo-server[4216]: }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.866Z xo:backups:worker INFO backup has ended

[pierrebrunet]

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

[Andrew]

@pierrebrunet It's a warning. Backup job is successful.

[pierrebrunet]

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

[FagnerMoraes]

Hello again,

When running the backup routine to the NAS, it is not saving the file anymore.

Please check the image showing:

the backup routine,
the path it points to on the NAS,
and the contents of the folder.

The .XVA file was not saved.

[FagnerMoraes]

On the S3 storage, the backup is being saved correctly and the old files are not being deleted unexpectedly.

Using the same backup configuration, the directory cleanup process is not executed twice there.

[pierrebrunet]

@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

[pierrebrunet]

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

[FagnerMoraes]

This post is deleted!

[FagnerMoraes]

@pierrebrunet
thats a metadata backup works fine, no alerts and no clean directory.
Metadata works fine.txt

[FagnerMoraes]

@pierrebrunet thats a metadata backup works fine:
Metadata works fine.txt

[pierrebrunet]

@FagnerMoraes Is your backup encrypted?

[pierrebrunet]

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

@pierrebrunet yes is encrypted!