<![CDATA[XO cant Snapshot itself ?]]>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

]]>https://xcp-ng.org/forum/topic/7154/xo-cant-snapshot-itselfRSS for NodeSat, 18 Apr 2026 13:29:46 GMTFri, 31 Mar 2023 07:12:25 GMT60<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 07 Jul 2024 19:08:54 GMT]]>@julien-f Thanks a lot for this update!

]]>https://xcp-ng.org/forum/post/79854https://xcp-ng.org/forum/post/79854Sun, 07 Jul 2024 19:08:54 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Mon, 01 Jul 2024 09:05:20 GMT]]>@wilsonqanda Exactly, under the hood that's precisely what XO is doing, it's calling VM.snapshot with the ignore_vdis param.

]]>https://xcp-ng.org/forum/post/79496https://xcp-ng.org/forum/post/79496Mon, 01 Jul 2024 09:05:20 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 30 Jun 2024 20:33:53 GMT]]>@julien-f Thanks a lot Julien. So this going to be implemented in next release?

So when I run [NOSNAP] it will ignore these VDI with [NOSNAP] at the beginning of the name but just wondering when loading from the snapshot those [NOSNAP] vdi won't be loaded so i just have to add them in to the disk tab so it can be boot back up like normal correct? This is the default case currently when running snippet below.

xe vm-snapshot new-name-label="newname_YYYY-MM-DDTHH:MM:SS.sssZ" uuid=vmUUID ignore-vdi-uuids=uuid1
]]>https://xcp-ng.org/forum/post/79478https://xcp-ng.org/forum/post/79478Sun, 30 Jun 2024 20:33:53 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Thu, 27 Jun 2024 13:38:58 GMT]]>It's implemented: https://github.com/vatesfr/xen-orchestra/commit/dcf6885dfaec000e93e4630307fe9d2d7fd66232

Thanks everyone for your feedback.

0 julien-f committed to vatesfr/xen-orchestra 
feat(xo-server): support `[NOSNAP]` tag on disks

Fixes https://xcp-ng.org/forum/post/79179
]]>https://xcp-ng.org/forum/post/79316https://xcp-ng.org/forum/post/79316Thu, 27 Jun 2024 13:38:58 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Thu, 27 Jun 2024 09:16:34 GMT]]>@olivierlambert Completely separate [NOSNAP] (for non-backup snapshots) and [NOBAK] (for backups) would be fine by me.

]]>https://xcp-ng.org/forum/post/79315https://xcp-ng.org/forum/post/79315Thu, 27 Jun 2024 09:16:34 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 23 Jun 2024 21:39:14 GMT]]>@Gheppy Wow great illustration πŸ™‚ i think this is perfect but only if it is feasible to implement it now...

FYI as a side note I notice that when I do ignore-vdi-uuids=uuid1,uuid2,uuid3 I notice that when I reload snapshots of the VM the ignore vdi(s) disappear in the Disks section. Which makes logical sense as those ignore-vdi-uuids are not part off the list that are snapshotted. But it's a bit of an inconvenient to add VDI back in as those vdi should still be part of the disk just not part of the snapshots. But otherwise it works great.

To snapshot do the following to ignore certain vdi(s):

xe vm-snapshot new-name-label="newname_YYYY-MM-DDTHH:MM:SS.sssZ" uuid=vmUUID ignore-vdi-uuids=uuid1

where uuid1=[NOSNAP] TESTING
e9a2aa43-a1ce-4616-99df-bdaada587151-image.png

Once reload the [NOSNAP] disappear:
74a25d27-1b2e-4968-844c-799ab2dc1742-image.png

Beside that this is the best workaround for now and this little inconvenience is not a big deal. But in case someone need to understand it hopefully I added enough detail to clarify this content for future readers.

]]>https://xcp-ng.org/forum/post/79183https://xcp-ng.org/forum/post/79183Sun, 23 Jun 2024 21:39:14 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 23 Jun 2024 20:12:44 GMT]]>This is what I was thinking

  • [NOSNAP] to be like SDA and disk 3
  • [NOBAK] to be with SDA and disk 2
  • In both cases disk 4 is excluded

66a42055-8a10-4b46-a203-0dd3da2e9b54-image.png

]]>https://xcp-ng.org/forum/post/79182https://xcp-ng.org/forum/post/79182Sun, 23 Jun 2024 20:12:44 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 23 Jun 2024 19:16:59 GMT]]>Opinion @julien-f ?

]]>https://xcp-ng.org/forum/post/79180https://xcp-ng.org/forum/post/79180Sun, 23 Jun 2024 19:16:59 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 23 Jun 2024 18:59:44 GMT]]>From my point of view, it should be with "OR" and if the condition is fulfilled to execute.
E.g :

  • if I have "[NOSNAP] 'VM name' " not to execute snapshoot
  • if I have "[NOBAK] 'Vm name' " not to execute backup
  • if I have "[NOSNAP] [NOBAK] 'Vm name' " not to execute snapshot and backup
    But if you make a backup, remove only what is with [NOBAK]
]]>https://xcp-ng.org/forum/post/79179https://xcp-ng.org/forum/post/79179Sun, 23 Jun 2024 18:59:44 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 23 Jun 2024 17:04:07 GMT]]>@olivierlambert Thanks for the quick reply. [NOBAK] works for backup by ignoring VDI with [NOBAK] in its name, but when running manual snapshot like stated above the [NOBAK] still show up in the SR meaning it made a copy of the [NOBACK].

Ideally with [NOBAK] it should not take snapshot or backup right or am i understanding it incorrectly? Does this only apply to automated BACKUP & SNAPSHOT only?
94bcd9f6-3051-46f1-91c8-729e4f289d43-image.png

]]>https://xcp-ng.org/forum/post/79178https://xcp-ng.org/forum/post/79178Sun, 23 Jun 2024 17:04:07 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 23 Jun 2024 12:21:05 GMT]]>You mean [NOBAK]?

]]>https://xcp-ng.org/forum/post/79174https://xcp-ng.org/forum/post/79174Sun, 23 Jun 2024 12:21:05 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sun, 23 Jun 2024 10:21:09 GMT]]>@julien-f @olivierlambert
Was there a resolution on the [NOSNAP] feature just much convenient than going to the CMD each time πŸ™‚ ?

In the meantime will be using snippet below so low priority for me:

xe vm-snapshot new-name-label=newname uuid=vmUUID ignore-vdi-uuids=uuid1,uuid2,uuid3
]]>https://xcp-ng.org/forum/post/79170https://xcp-ng.org/forum/post/79170Sun, 23 Jun 2024 10:21:09 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Wed, 10 May 2023 17:29:17 GMT]]>The situation I can have in mind:

  • you want your VM to be backup
  • when you do a manual snapshot, you don't want to snap a disk

But why doing this? I don't know, it's hard to predict the need for this… At least, if we choose to NOT doing a backup of this disk with NOSNAP, we MUST tell that clearly in the doc.

]]>https://xcp-ng.org/forum/post/62067https://xcp-ng.org/forum/post/62067Wed, 10 May 2023 17:29:17 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Wed, 10 May 2023 16:45:34 GMT]]>I don't see a case where one would want [NOSNAP] but not [NOBAK]. Maybe we could require either none or both of them during a backup and not support one without the other?

]]>https://xcp-ng.org/forum/post/62065https://xcp-ng.org/forum/post/62065Wed, 10 May 2023 16:45:34 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Wed, 10 May 2023 16:43:46 GMT]]>@olivierlambert I think that [NOSNAP] means that this VDI should not be snapshotted and that ignoring it during backup would be surprising.

But your point is valid too, I have no ideal solution, hence my question ^^

]]>https://xcp-ng.org/forum/post/62064https://xcp-ng.org/forum/post/62064Wed, 10 May 2023 16:43:46 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Wed, 10 May 2023 16:40:10 GMT]]>That's a good question and an important choice to make πŸ€”

IMHO, the principle of least surprise would tell to ignore [NOSNAP] during a backup. Because I'm afraid people would backup a VM with [NOSNAP] and expect it to be saved. That would be a bad surprise if not. What do you think?

]]>https://xcp-ng.org/forum/post/62062https://xcp-ng.org/forum/post/62062Wed, 10 May 2023 16:40:10 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Wed, 10 May 2023 16:29:51 GMT]]>@olivierlambert Does [NOSNAP] implies [NOBAK]?

If not, should we ignore [NOSNAP] when a snapshot is required to backup the VM?

]]>https://xcp-ng.org/forum/post/62060https://xcp-ng.org/forum/post/62060Wed, 10 May 2023 16:29:51 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Mon, 03 Apr 2023 03:37:56 GMT]]>@Meth0d Format wise I am using EXT so it's thin provisioned, and since it's all thin provisioned, snapshots only take up the space of the changes to the disk, so you don't really need enough space for 8TB snapshots.

As for LVM, you mean in the VMs to manage spanning? So far I've only really had a need to go beyond 2TiB for Windows VMs so I'm just using NTFS with Windows Disk Manager for those spans. But I imagine you could do it with LVM in Linux, not sure if there are better options for it.

]]>https://xcp-ng.org/forum/post/60714https://xcp-ng.org/forum/post/60714Mon, 03 Apr 2023 03:37:56 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Sat, 01 Apr 2023 09:26:42 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/60654https://xcp-ng.org/forum/post/60654Sat, 01 Apr 2023 09:26:42 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Fri, 31 Mar 2023 18:58:05 GMT]]>FYI just for future things, a generally better way to make greater than 2TiB disks is to simply span them within the guest OS, so basically for 7TiB just make like 4 2TiB VHD's and then have the VM OS span those disks so they appear as a single disk within the VM.

I do this all the time, works super well and gives you the ability to still snapshot them, etc....

]]>https://xcp-ng.org/forum/post/60628https://xcp-ng.org/forum/post/60628Fri, 31 Mar 2023 18:58:05 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Fri, 31 Mar 2023 13:56:20 GMT]]>We have to discuss this internally with @julien-f πŸ™‚

]]>https://xcp-ng.org/forum/post/60611https://xcp-ng.org/forum/post/60611Fri, 31 Mar 2023 13:56:20 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Fri, 31 Mar 2023 13:54:46 GMT]]>Thanks for the heads up. A [NOSNAP] Feature sounds like a good idea though πŸ™‚

]]>https://xcp-ng.org/forum/post/60610https://xcp-ng.org/forum/post/60610Fri, 31 Mar 2023 13:54:46 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Fri, 31 Mar 2023 12:56:56 GMT]]>You can do this on the cli (in 8.3) via

xe vm-snapshot new-name-label=newname uuid=vmUUID ignore-vdi-uuids=uuid1,uuid2,uuid3

It is currently not possible in Xen-Orchestra, see
https://xcp-ng.org/forum/topic/3607/snapshot-backup-exclude-additional-mounted-disk/8?_=1680267126156

]]>https://xcp-ng.org/forum/post/60597https://xcp-ng.org/forum/post/60597Fri, 31 Mar 2023 12:56:56 GMT<![CDATA[Reply to XO cant Snapshot itself ? on Fri, 31 Mar 2023 12:31:57 GMT]]>
  • On XCP-ng 8.2: [NOBAK] will be only used by Xen Orchestra to NOT export the snapshot generated by VM.snapshot method.
  • On XCP-ng 8.3: [NOBAK] will be used by XO to exclude the disk from the VM.snaphot call during an XO backup (since we added that feature in XAPI ourselves)

    • In any case, a manual snapshot will snap all the drives.

    ]]>    https://xcp-ng.org/forum/post/60592https://xcp-ng.org/forum/post/60592Fri, 31 Mar 2023 12:31:57 GMT