@olivierlambert Thanks Olivier,

That report wasn't up yet when I ran into this yesterday, and I confess to not having looked this morning since I continued.

My assumptions were:

• It's 99% likely to be my config and not a code issue.
• Github support requests for source builds tend to be told to use the community forum instead

Hence posting here. Wasn't expecting a staff response, but appreciate it! I'll have a look at reverting to the suggested commit as @julien-f proposes. Commercial XOA isn't in the budget, but I appreciate the suggestion for that, too!

Haven't been able to find an anwer to this elsewhere - so no doubt the first reply will be a link to someone answering this three days ago. In advance of that: Sorry, I tried!

The cluster we're running this on has VM's that vary between about 2.5GB actual-size-of-vdi to about 130GB. Lets say there's 15 VM's in a job and a concurrency of five.

What criteria does XO use to order the backup jobs in that scenario - how does it pick which five "go first"?

@olivierlambert It's a fair trade.

@olivierlambert

Appreciate that! Don't suppose you're up for tagging or branching this commit as a defined release, are you?

But more seriously - I can also confirm that backups now work on my installation by reverting to commit 350b0c1e3cf600ecb7c75f76daeae93d44a37121.

@olivierlambert Thanks Olivier,

That report wasn't up yet when I ran into this yesterday, and I confess to not having looked this morning since I continued.

My assumptions were:

• It's 99% likely to be my config and not a code issue.
• Github support requests for source builds tend to be told to use the community forum instead

Hence posting here. Wasn't expecting a staff response, but appreciate it! I'll have a look at reverting to the suggested commit as @julien-f proposes. Commercial XOA isn't in the budget, but I appreciate the suggestion for that, too!

After a few other issues, I'm now running as root, I've enjoyed the confusion of watching my xcp-ng controller try and unmount my / partition and I'm trying to get backups working.

No errors in the command line:

2021-02-19T11:50:26.905Z xo:main INFO + WebSocket connection (::ffff:172.16.32.167)
2021-02-19T11:50:55.654Z xo:xapi DEBUG Snapshotting VM wpwtj as [XO Backup barber backup test] wpwtj
2021-02-19T11:51:03.693Z xo:xapi DEBUG exporting VDI wpwtj

but the web interface gives the following:

Error: The "path" argument must be of type string. Received an instance of IncomingMessage

This is node 12 straight from the nodesource repos, yarn run v1.22.10 straight from their repos, and latest XO from the vates repos - on Ubuntu 12.04 with latest patches. Hosts are running XCP-ng 8.2LTS also with the latest patches.

I've been accessing XO through an nginx reverse proxy (nginx 18, straight from their repos), but in order to reduce possible failure points I'm now connecting directly to the xo web interface with no tls, running on port 2080. The backup is the first of a backup of type Delta, VM manually selected, to an NFS remote. The same remote is working fine for a metadata backup.

As an experiment, I tried switching from a Delta Backup to a Backup, which changed the error to:

Error: The "path" argument must be of type string. Received an instance of Transform

Any ideas?

Many thanks to all!