XO Community edition backups dont work as of build 6b263
-
The rebuild maybe?
-
@RobWhalley to see if it's behaving the same as what I saw on prior versions can you do the following steps?
-
open tasks in a new browser window so you can monitor it. If you can keep the backup window and task window side by side you can see if the export command comes and goes quickly.
1.a If you go between backup and tasks in the same window, ive noticed the prior task history clears out. -
ssh into the VM running XO and monitor the syslog
tail -100f /var/log/syslog
#may need root then try sudo tail -100f /var/log/syslog -
In primary window kick off a backup then watch the task window to see if export command comes and goes.
-
If the task disappears then click on previous tasks and see if you even had export command come up.
-
reply with the results of how task shows export step and any errors in the syslog file.
Hopefully that helps the devs figure out whats going on in your system.
-
-
Also maybe
xo-server -h
can give the info we need -
Thanks both for the help, it's much appreciated.
@olivierlambert - apologies, I'm having some difficulty in finding
xo-server
... the closest I can find is a mention to it in/opt/xo/xo-src/xen-orchestra/packages/xo-server/xo-server.service
:ExecStart=/usr/local/bin/xo-server
# /usr/local/bin/xo-server bash: /usr/local/bin/xo-server: No such file or directory
However, when I check
/etc/systemd/system/xo-server.service
, I get something quite different:ExecStart=/opt/xo/xo-server/dist/cli.mjs
This file does exist, but running it with
-h
doesn't seem to provide a useful output:# /opt/xo/xo-server/dist/cli.mjs -h Usage: xo-server [--safe-mode] xo-server v5.180.1
I can run the script in place of the service, but in terms of output it only gives me the same as the
journalctl -u xo-server
output (see previous attachment):# systemctl stop xo-server # /opt/xo/xo-server/dist/cli.mjs
2025-06-30T15:00:42.871Z @xen-orchestra/xapi/disks/Xapi WARN can't connect through NBD, fallback to stream export 2025-06-30T15:00:42.892Z xo:backups:worker WARN possibly unhandled rejection { error: RequestAbortedError [AbortError]: Request aborted at BodyReadable.destroy (/opt/xo/xo-builds/xen-orchestra-202506301106/node_modules/undici/lib/api/readable.js:51:13) at XapiVhdStreamSource.close (file:///opt/xo/xo-builds/xen-orchestra-202506301106/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:160:22) at XapiStreamNbdSource.close (file:///opt/xo/xo-builds/xen-orchestra-202506301106/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:34:29) at XapiStreamNbdSource.close (file:///opt/xo/xo-builds/xen-orchestra-202506301106/@xen-orchestra/xapi/disks/XapiStreamNbd.mjs:81:19) at #openNbdStream (file:///opt/xo/xo-builds/xen-orchestra-202506301106/@xen-orchestra/xapi/disks/Xapi.mjs:92:21) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async XapiDiskSource.openSource (file:///opt/xo/xo-builds/xen-orchestra-202506301106/@xen-orchestra/xapi/disks/Xapi.mjs:198:18) at async XapiDiskSource.init (file:///opt/xo/xo-builds/xen-orchestra-202506301106/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:28:41) at async file:///opt/xo/xo-builds/xen-orchestra-202506301106/@xen-orchestra/backups/_incrementalVm.mjs:67:5 at async Promise.all (index 0) { code: 'UND_ERR_ABORTED' } }
@marcoi - I didn't see anything appear other than this:
Edited to correct screenshot
-
@RobWhalley I see in the error it mentioning NDB, do your backups have that enabled?
can you try disabling it and testing backup if you do have it on? I think i saw someone else post issue with NDB code in the forums.
-
Thanks @marcoi - I don't believe so, though I have no experience of the Network Block Device protocol. The VMs are backed up to a NFS share on a Synology NAS, so pretty low tech in comparison to what a lot of folks here will be using. Based on this page, I'm guessing NBD isn't natively supported on these devices?
This is a sample of the settings, let me know if you need any further information:
-
@RobWhalley Okay you have similar setup to me then. Can you confirm NFS share for backup is working and enabled?
it under settings -->Remote
Make sure the enabled is green and try clicking on the test icon in far right.
-
@marcoi Good thinking, here we go - seems OK:
I think I neglected to mention that while backups using the Delta Backup mode failed, other modes have been working:
-
@RobWhalley lol i forgot to test deltas - let me see on that.
-
scratch that prior comment. My backups are all setup as delta backup with schedule 2nd run that forces full backup. So i believe both are working correctly.
if you can also try deleting all the backup snapshots of the VMs in the backup and running full backup then the delta backup jobs.