@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

pierrebrunet289 opened this pull request in vatesfr/xen-orchestra

closed fix (XO Hub): read getResourceCatalog removed during refactor #9362

@probain Thank you!

Thank you @acebmxer , it should be fixed by https://github.com/vatesfr/xen-orchestra/pull/8907

pierrebrunet289 opened this pull request in vatesfr/xen-orchestra

closed fix(backup): set transfer tag only on AbstractRemote #8907

@flakpyro Hi, I am looking into it.

@Pilow perfect!

@Pilow ooh sorry, I did not see that you have a proxy. You need to fix it in the proxy too.

Edit: in fact, you just have to put the changes of IncrementalRemoteWriter.mjs in proxy node_modules, the rest is optional

@Tristis-Oris
Hi,
Thank you for your feedback.
A fix is currently in review for release. It will be available soon.

@probain Hi,
Great!! Can you confirm the checkbox is in the Service Provider Details window? It is to enhance the doc part about SAML.

@Mathieu Thanks to your help, we are deploying a patch with config update and control over document and assertion signatures
https://github.com/vatesfr/xen-orchestra/pull/9093

pierrebrunet289 opened this pull request in vatesfr/xen-orchestra

closed fix(plugin/auth-saml): add default config in SAML #9093

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

@ducatijosh Hi,
Can you check git status to see if you have anything tracked in your repository? You need to wait for a new commit in master though.

@jvanabra "merge synchronously" option is there for log purpose. When you click on your backup job you can get all logs from this job here:

Your chain seems to have an issue. Can you recreate your snapshot to reset the chain?
Furthermore, can you check the option "merge backup synchronously" to see what is happening in merging part.

PS: in case you have a license, feel free to open a ticket.

@jvanabra Hi,
Can you provide the complete logs from your backup job please? We changed a lot of things in backup recently but we did not have this kind of error.
Regards,

@TechGrips Sorry, there is no quick test to be sure the VM is not corrupted. The usual way would be to make a healthcheck. We cannot be sure everything is ok as it concerns multiple tar linked to each other. If it keeps warning you on the same backups, it may be due to a faulty parent. You would need for this to create a new chain of snapshot

@TechGrips Hi,
Unused XVA means a XVA file is not linked to any metadata (to remove a backup, we first remove the metadata file linked to it, then we remove the XVA), it should be removed by clean vm step. It is not an issue, just an information.

For the second warning "XVA might be broken", this is because the compressed file seems to be corrupted but we cannot be sure. We prefer to warn the user there may be an issue in the file. This should encourage to remake a backup.

@flakpyro Hi, it seems it is a race condition between disk check and close, and disk transfer. That's why it is randomly happening. This is not an easy fix, we are trying to figure out a workaround.

@flakpyro Hi, I am looking into it.

@Pilow perfect!