@pedro_udifar Please update to the latest code base and then let us know if you still encounter this issue.

@pierrebrunet said: Another thing to check is the exact time between your XO and your host. I installed the host with NTP from "static" DHCP (OK according to https://docs.xcp-ng.org/installation/requirements/) not made any manual changes/configs After I did a RTC adjustment in BIOS 3 days ago, the time now is ~1s ahead This is the output from timedatectl [22:04 x2 ~]# timedatectl status Local time: tor 2026-07-16 22:06:45 CEST Universal time: tor 2026-07-16 20:06:45 UTC RTC time: tor 2026-07-16 20:06:42 Time zone: Europe/Stockholm (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at sön 2026-03-29 01:59:59 CET sön 2026-03-29 03:00:00 CEST Next DST change: DST ends (the clock jumps one hour backwards) at sön 2026-10-25 02:59:59 CEST sön 2026-10-25 02:00:00 CET NTP synchronized: no I thought that the time would be adjusted automatically at reboot The first NTP sync should allow a bigger step than when it's already synced. @pierrebrunet said: do you make these backup regularly? They run once a day @ 03:04 before the normal backup that starts @ 03:10 and they have all run OK since July 8, the failed one reported 8 days ago ( post ~85 ) Maybe you should resync your clock NTP is enabled but not synced, I don't know the correct way to sync it In xsconsole/ I tried Use DHCP NTP Servers It changed the RTC clock to the same as UTC time but time was still 1s ahead and NTP not synced. I rebooted the host and I got this: [23:36 x2 ~]# timedatectl status Local time: tor 2026-07-16 23:37:17 CEST Universal time: tor 2026-07-16 21:37:17 UTC RTC time: tor 2026-07-16 21:37:16 Time zone: Europe/Stockholm (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at sön 2026-03-29 01:59:59 CET sön 2026-03-29 03:00:00 CEST Next DST change: DST ends (the clock jumps one hour backwards) at sön 2026-10-25 02:59:59 CEST sön 2026-10-25 02:00:00 CET NTP still not synced, Local time 2s ahead, RTC 1s ahead, I don't know, If not someone can show me the proper way to manually resync, maybe I should try to reinstall the host

@simonp , thank you very much and all of your team ! ! ! Keep up the outstanding work. Regards, Marc

@pierrebrunet Hello! I've checked B2 logs and found some errors like you had foreseen. I had a look and this kind of 500 INTERNAL ERROR several times on other jobs that seem ok. How many retries does XO attempt to send the part when this happens? I'll do another run that includes only a few large VMs. BTW, is there a way to interrupt the job withou restarting XO ? REST.PUT.PART Weekly/xo-vm-backups/60b4d2a7-3f91-f0f9-b0a0-f834df3ff9ee/20260705T070618Z.xva "PUT /zzzzzkly/xo-vm-backups/60b4d2a7-3f91-f0f9-b0a0-f834df3ff9ee/20260705T070618Z.xva?partNumber=3954&uploadId=4_ze092693d1b65962e9fe6051b_f25969add7e42e384_d20260713_m140016_c003_v0312040_t0013_u01783951216751&x-id=UploadPart HTTP/1.1" 500 INTERNAL_ERROR 145 - 3762 3762 "-" "aws-sdk-js/3.1065.0 ua/2.1 os/linux#5.15.0-185-generic lang/js md/nodejs#24.18.0 api/s3#3.1065.0 m/N,a,c,E,e xen-orchestra-fs-4.9.2" - - - TLS_AES_256_GCM_SHA384 AuthHeader s3.eu-central-003.backblazeb2.com TLSv1.3 - -

Hi @acebmxer, thanks for reporting, we identified this bug internally already, we're going to fix it once root cause is found.

Hi Everyone, If I may advertise what I did you have a dedicated thread about my project, this is an easy to setup XCP-ng and XO from the source solution. Sorry sharing the link to the topic as is couldn't find better way to do that : XCP-ng HL — an ISO for home labs, deploy any XOA image from XO Lite directly Essentially you deploy XCP-ng ISO and then in XO Lite deploy XOA section you can deploy your prebuilt or XOA VM directly. Hope that helps Home labers to get in to XCP-ng easily. Same here this is still work in progress, also I'm personally already using this version in my lab. Any feedback is welcome ! With regards.