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.
@planedrop are you using LVM for that or how are u doing that? I never bothered with the problem because i dont have enough local space for 8TB disk snapshots anyways.
Thanks for the heads up. A [NOSNAP] Feature sounds like a good idea though 
@olivierlambert maybe i missunderstood things, the RAW Disk from my XO VM is the 7TB data disk "[NOBAK] xoa_backup_hdd".
The system disk is "xoa_sda" is not RAW.
So i thought excluding the disk with "[NOBAK]" would make me able to snapshot the VM (system disk). So whenever you have attached a RAW device makes you unable to snapshot the VM.
Detaching it, taking a snapshot and reattaching it would work however?
@olivierlambert Okay but obviously i can create snapshots on the RAW SR (here OPensense in the screenshot above). So this is a should but bould sometiomes does work situation ?-)
@olivierlambert Yes i think it is, if i remember correct that was the only way to add +4TB drives ?
I just tested to do a snapshot from another VM on that disk, that works.
@olivierlambert Well its virtual disk is located on a local attached 8TB Disk .....
@olivierlambert
Its running on a Local attached 8TB Disk thats also used to Store the Backups
I was trying to take a Snapshot from my XOA (Source) VM before updating it but aparently i cant:
vm.snapshot
{
"id": "4ac34777-312e-cb6e-67a0-ccc34a71f8e1"
}
{
"code": "UNIMPLEMENTED_IN_SM_BACKEND",
"params": [
"OpaqueRef:662bcb78-4ffa-4c26-8d82-c5197d7c7e07"
],
"task": {
"uuid": "a24d6e0f-04cf-039d-b0bb-6a53589f9874",
"name_label": "Async.VM.snapshot",
"name_description": "",
"allowed_operations": [],
"current_operations": {},
"created": "20230331T07:07:23Z",
"finished": "20230331T07:07:24Z",
"status": "failure",
"resident_on": "OpaqueRef:7a2e10b8-677f-4c65-95cd-b8393884450b",
"progress": 1,
"type": "<none/>",
"result": "",
"error_info": [
"UNIMPLEMENTED_IN_SM_BACKEND",
"OpaqueRef:662bcb78-4ffa-4c26-8d82-c5197d7c7e07"
],
"other_config": {},
"subtask_of": "OpaqueRef:NULL",
"subtasks": [
"OpaqueRef:b2436483-c1ee-447c-8016-636a52c61528"
],
"backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 80))((process xapi)(filename list.ml)(line 110))((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 122))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 35))((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 130))((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 171))((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 209))((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 220))((process xapi)(filename list.ml)(line 121))((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 222))((process xapi)(filename ocaml/xapi/xapi_vm_clone.ml)(line 442))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 35))((process xapi)(filename ocaml/xapi/xapi_vm_snapshot.ml)(line 33))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 131))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/xapi/rbac.ml)(line 233))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 104)))"
},
"message": "UNIMPLEMENTED_IN_SM_BACKEND(OpaqueRef:662bcb78-4ffa-4c26-8d82-c5197d7c7e07)",
"name": "XapiError",
"stack": "XapiError: UNIMPLEMENTED_IN_SM_BACKEND(OpaqueRef:662bcb78-4ffa-4c26-8d82-c5197d7c7e07)
at Function.wrap (/opt/xen-orchestra/packages/xen-api/src/_XapiError.js:16:12)
at _default (/opt/xen-orchestra/packages/xen-api/src/_getTaskResult.js:11:29)
at Xapi._addRecordToCache (/opt/xen-orchestra/packages/xen-api/src/index.js:984:37)
at forEach (/opt/xen-orchestra/packages/xen-api/src/index.js:1018:14)
at Array.forEach (<anonymous>)
at Xapi._processEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:1008:12)
at Xapi._watchEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:1181:14)
at runNextTicks (node:internal/process/task_queues:60:5)
at processImmediate (node:internal/timers:447:9)
at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}
Every other VM on that host i can snapshot just fine.
I even tried shutting it down and then taking a snapshot with the same result.
8.2.1 Host is Up2Date
@olivierlambert i have created config.httpInactivityTimeout.toml in /opt/xen-orchestra/packages/xo-server with the content from above. Not sure how i can check if thats actually set.
BTW: this is not a CR Backup Problem, i also dont see Tasks running for my "normal" Backup Job. I cant check "how far" the actual Backup runs and if that differs.
@Darkbeldin there is enough space for the snapshot and on the remote. How can i investigate the root rause further?
