@johnnezero You can use the docs directly in /rest/v0/docs. You just have to connect and fill in the uuid you need. It will work

@johnnezero Hi,
Sorry, it seems it is only in Rest API for now:
You can check it here:

<xoa-url>/rest/v0/docs/#/backup-repositories/ReclaimSpaceBackupRepository

@johnnezero It just came out with the release... now
Just one thing, you may have empty directories even after the reclaimSpace task but they should be empty

@henri9813 Hi,
There should be a new "reclaimSpace" in next release which help you to clean repositories.

Just to let you know, we prefer to not remove orphan backups in case a VM removal is accidental and you want to bring back it from a backup repository

@Andrew This branch is now merged, thank you for your feedback!

@jr-m4 Hi,
We have found this issue in another thread, it is now merged

@manilx @andrew @abudef @robertblissitt
Here is the branch we are working on: https://github.com/vatesfr/xen-orchestra/tree/fix_alias_vhd

It should fix the issue, in case you have time to test it

@Andrew Hi,
I am on it, thank you for the report!

@abudef Hi,
Do you think this doc can help you?

Link to doc

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

@acebmxer @flakpyro Hi, there was a patch release this morning for a few issues. Can you update your XO and check if it still happen?

@pedro_udifar Hi,
Do you still have errors 500 when you are talking about general errors?

@JB @majorp93 We made a smaller PR to be merged just after the release (because it is linked to almost all XAPI calls), the new branch is this one if you want to test: fix_undici_timeout
Same fix, just a little smaller

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

@acebmxer ok, too bad... I thought we had it...
@majorp93 this can be a lead. I will ask xapi team if they changed something in pool metadata export.

@MajorP93 Hi,
Thank you, thank you! I think you found it! It seems to be SMB, @acebmxer can you confirm that you also use smb please?
If this is the case, the bad news is I think we will need to update our docs to not advise SMB at all: it was already said for delta but maybe we will have to extend this to all kind of BR

@pedro_udifar Hi,
You can try again with minPartSize=100000000 indeed. But I would advise you to contact B2 directly. They should have a clearer error to show instead of a 500.
Thanks for your patience and your help

@pedro_udifar This is indeed a particular case. Can you switch xo-server log to debug please? Then we would need the journalctl from your xo-server. You can give it to me through MP if you prefer.