Ok thanks!

I'm using Xen Orchestra Community Edition.

When I click on Stats for VM's it simply says "No Stats".

It appears the issue is only with XO as I can use XCP-NG Center v20.04.01 and see stats.

When I click on XO logs i get this error:

vm.stats
{
  "id": "bd624d23-6d7d-a1f0-791d-541e91351bb5",
  "granularity": "seconds"
}
{
  "message": "unusable",
  "name": "TypeError",
  "stack": "TypeError: unusable
    at /opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/undici/lib/api/readable.js:224:34
    at Promise._execute (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/bluebird/js/release/debuggability.js:384:9)
    at Promise._resolveFromExecutor (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/bluebird/js/release/promise.js:518:18)
    at new Promise (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/bluebird/js/release/promise.js:103:10)
    at consume (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/undici/lib/api/readable.js:212:10)
    at BodyReadable.text (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/undici/lib/api/readable.js:111:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202409281449/packages/xo-server/src/xapi-stats.mjs:258:39
    at XapiStats._getAndUpdateStats (file:///opt/xo/xo-builds/xen-orchestra-202409281449/packages/xo-server/src/xapi-stats.mjs:319:18)
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202409281449/@vates/task/index.js:169:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202409281449/@vates/task/index.js:153:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202409281449/packages/xo-server/src/xo-mixins/api.mjs:402:20)"
}

Sorry, you are right. The first time it didn't start and didn't show an error??
I just ran the job again with successful backup and it started without issue.

I'm using XOCE and have setup backups for my VM's. I set a Delta backup that included my one Window Machine that gave me an error (insufficient storage space error). I then created a separate backup job solely for the windows machine and used the offline line backup setting. The job works and shuts down the VM and the backup succeeds, but the VM stays off. Is there an Auto start VM feature after the backup job is done? I can't seem to find such a feature.