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.
@Andrew Hi,
I am on it, thank you for the report!
@abudef Hi,
Do you think this doc can help you?
I think it needs some improvements, feel free to enhance it if you feel it is necessary!
@JB @christopher-petzel Thanks for your patience! We are glad it works well!
@acebmxer Hi, I just checked your infra. It seems there was a connection error on the proxy around 2h ago: "Xen Orchestra Server could not be reached. Please check your connection."
Can you retry a backup whenever it is possible for you?
Edit: for this part, "error": "Having multiple authentication methods is not supported, please choose one"
It is because you are connecting with two connections in parallel (one with a token and one basic).
@pedro_udifar Hi,
Do you still have errors 500 when you are talking about general errors?
@gsszuber Hi,
Yes indeed, you need to preserve the root of the bucket from Lifecycle. We just had a customer with a similar issue.
Can you help us by giving a small screenshot of the field to filter out the root (or filter in the three folders) please?
@bogikornel are you talking about another issue? We are on an issue specifically on "pool metadata backups". It seems you are talking about VM backups. If yes, can you send the backup log please?
