I noticed my backup report was missing from my inbox, when i look into XOA the plugin is disabled.

When i try to enable it (with the old settings):
Log: strict mode: unknown keyword: "enumNames"

I tried to delete configuration but end up with the same result after i re-entered all credentials.

I just rebuild from source, still the same.

Hmm it sounded like SR_BACKEND_FAILURE_79 would only mean one thing as its the same error when you try to create a disk > 2TB. But i know nothing about all that.

"stack": "XapiError: SR_BACKEND_FAILURE_79(, VDI Invalid size [opterr=VDI size must be between 1 MB and 2088960 MB], )

@olivierlambert yeah i found that later.
The XO message could be more informative though

Oh i might have found the issue here

Aug 24 13:13:16 xcp-ng SM: [6430] Raising exception [79, VDI Invalid size [opterr=VDI size must be between 1 MB and 2088960 MB]]

So i cant migrate anything with disks larger 2TB or is there a workaround?

I am trying to move a (rather large) VM from one 8.2 Host to another 8.2 host.
Both are up2date, one needs to run kernel-alt though.

After an hour of copying at around 60MiB the Job fails (the VM has around 6TB in 3 disks):

vm.migrate
{
  "vm": "3db79843-7d43-b13a-2d20-30e2297a700c",
  "mapVifsNetworks": {
    "c89c9bb7-ffba-b8ec-9e5a-d3290102c8eb": "6848e2c6-9ffc-66c8-55c3-a564317a1ae1"
  },
  "migrationNetwork": "6848e2c6-9ffc-66c8-55c3-a564317a1ae1",
  "sr": "85ad8902-0114-6a20-cc80-2f474f25e7c2",
  "targetHost": "a2b237fb-669f-4fbc-803b-33077b723aac"
}
{
  "code": 21,
  "data": {
    "objectId": "3db79843-7d43-b13a-2d20-30e2297a700c",
    "code": "SR_BACKEND_FAILURE_79"
  },
  "message": "operation failed",
  "name": "XoError",
  "stack": "XoError: operation failed
    at operationFailed (/opt/xen-orchestra/packages/xo-common/src/api-errors.js:21:32)
    at file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:482:15
    at Object.migrate (file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:469:3)
    at Api.callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:304:20)"
}

I have moved other (smaller) VMs in the same direction between these hosts.

@danp Thanks that worked.

@julien-f yes seems fixed, thanks.

@ci4ic4 how did you manage to update from 14.16 to 14.17 on Debian 10?

deb.nodesource.com/setup_14.x just seems to give me 14.16

Hmm something is off here.
I grabbed the latest node 14 from nodesource:

nodejs is already the newest version (14.17.0-deb-1nodesource1).

But:

root@xoa:~# node -v
v14.16.0

@danp Well I will try to update node later but since you got the exact same error something else seems to be going on.

error xo-server@5.79.5: The engine "node" is incompatible with this module. Expected version ">=14.17". Got "14.16.0"

Did someone bump that ?

Damn always when you forget to take a snapshot before trying to build from sources it fails