@olivierlambert No never changed it. From what i understand from Jon it's default this where his words "and all these SRs have auto-scan enabled. This means every 30 seconds, the pool master will scan the entirety of every SR". We changed this and the problem is gone.

Support found that automatic refresh of our sr every 30 seconds delayed this. It seems we had this for a longer time but now it’s more aggressive. Disabled this as this is not required. This resolves our issue here.

Anyone else experiencing this issue?
https://github.com/vatesfr/xen-orchestra/issues/8713

it's a long time bug that i believe is pretty easy to fix and get CBT backups to get more robust. Would be great if this can be implemented!

rtjdamen created this issue in vatesfr/xen-orchestra

open CBT backup fails repeatedly due to leftover invalid CBT snapshots #8713

Hi All,

are there other users running 8.3 combined with CBT backups? we keep running into vdi's that stay connected to the control domain, we are investigating these with Vates as it looks like the problem is within xapi of tapdisk it would be helpfull to understand if there are others running into the same issue.

As far as i understand from vates it looks like the problem we face is somewhere within Xapi but we need more logging to understand it better. If anyone has this running with the same issues or without please let us know so we can compare.

Cheers!

Hi All,

First of all best wished to you all for 2025! I have just deployed the latest build to do some testing on the one remaining issue we have with cbt backups, we were still facing full backups on some vms, this is expected to happen because cbt is not activated fast enough on some vdi’s, i will update this post once it completed some test runs to let u know if this build resolves it (there is a fix inside this build that should fix it).

Robin

@andyh no cbt should be disabled, u can’t migrate an cbt enabled vdi.

You need to remove all snapshots before migration and disable cbt. Storage migration is not supported when cbt is invalid. I believe xoa should do this automatically however.

@florent ok thanks, but how does this work for a job with multiple retentions? if i have a job with 3 schedules and retentions set for this job, how does the sequence handle this, in other words as the retention is set on the schedule level and i disable 1 of 3 schedules, how does the sequence know what retention it should keep?

@Andrew we see the same behavior here, no strange backup issues so far!

Hi all, i can confirm the vdi_in_use error is resolved by https://github.com/vatesfr/xen-orchestra/pull/7960 we no longer see issues there.

Only remaining issue we see is the “ can’t create a stream from a metadata vdi fall back to base”

fbeauchamp opened this pull request in vatesfr/xen-orchestra

closed feat(backups/CBT): retry data_destroy when error is VDI_IN USE #7960

@olivierlambert yes i will! I think it has to do with the poolmaster not getting the right information from all the slaves but maybe i am wrong. We detached one host this morning because of a broken mainboard so maybe the clue is there but maybe support can help!

@olivierlambert no we are using normal shared storage woth regular vdi we see this on all shared storage types nfs and iscsi

Hi,

We have been running XCP-ng 8.3 for some time already, but after deploying the latest XCP-ng 8.3 patches, Storage → Stats in Xen Orchestra no longer shows any statistics for our SRs.
The page only displays “No stats”.

Key points:
• This started after installing the most recent 8.3 updates, not immediately after upgrading to 8.3
• The issue affects SR stats only
• Host and VM stats are displayed correctly
• Storage itself is fully functional (VMs running, space usage correct)
• SR status is Connected (not partially connected)

Anyone familiar with this issue?
Robin

@olivierlambert Thank u, so for now these endpoinst are not in the restapi yet?

Hi all,

I’m wondering if it’s possible to change VM settings over the REST API — things like memory, disk size, or CPU count.
I’ve checked the Swagger documentation, but it doesn’t seem to include those endpoints.

From what I understand, XO6 is built on top of the same API that Xen Orchestra uses, so in theory these kinds of settings should be adjustable through the API as well.
Maybe I’m missing something, but I’d really appreciate if someone could point me in the right direction!

Thanks,
Robin

@olivierlambert No never changed it. From what i understand from Jon it's default this where his words "and all these SRs have auto-scan enabled. This means every 30 seconds, the pool master will scan the entirety of every SR". We changed this and the problem is gone.

Support found that automatic refresh of our sr every 30 seconds delayed this. It seems we had this for a longer time but now it’s more aggressive. Disabled this as this is not required. This resolves our issue here.

@florent so not an option solving this inside xoa? Could be usefull for the short term.

Anyone else experiencing this issue?
https://github.com/vatesfr/xen-orchestra/issues/8713

it's a long time bug that i believe is pretty easy to fix and get CBT backups to get more robust. Would be great if this can be implemented!

rtjdamen created this issue in vatesfr/xen-orchestra

open CBT backup fails repeatedly due to leftover invalid CBT snapshots #8713

@olivierlambert ok, maybe u experience some differences as well, we were on 8.3 since February and did patch last friday, since the patching is see a decrease.

What i believe is happening is that GC processes are blocking other storage operations. So only if a coalece is done on an sr i see multiple actions like destroy, enable cbt and change block calculations being processed. As far as i know this was not the case before, they also could take some longer but it was not related to (or i have never noticed it).

Maybe we can confirm if this behavior is by design or not?