@RobWhalley
That worked for me as well.

I created a new XenOrchestra VM with commit 3c543.

Enabling and disabling NBD on the backup job did the trick.

Thank you and everyone else for your efforts and digging into the matter.

Regards
Marc

I am giving a short "report", when there is new version out and I have tested it.

Nice weekend @y'all

Regards,
Marc

Hi @McHenry .

You should obfuscate the IP address in your first screenshot. Also check your profile and private chat

Hope everyone had a joyful Christmas and I wish everyone the best for 2026.

Regards,
Marc

Quick Update:

Was looking good with commit cf26d.

After the transfer completed the VDI of that particular VM was still in use, according to XO.

So still failure on the job.

Regards,
Marc

Hi @pierrebrunet.

I have deleted the "parentless" VDIs and snapshots.

So the "Unhealthy VDI" page is empty for me.

So everytime I retry with the VM in question it is creating a new (full) backup-chain.

Regards,
Marc

Problem still present in commit 04deb.

Here is the log from the XO6 interface:

"XapiError: VDI_IN_USE(OpaqueRef:ce1e2c1b-9b52-d813-88fc-18513a51306f, destroy)\n    
at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/_XapiError.mjs:16:12)\n    
at default (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/_getTaskResult.mjs:13:29)\n    
at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1078:24)\n    
at file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1112:14\n   
at Array.forEach (<anonymous>)\n    
at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1102:12)\n    
at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1275:14)\n   
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)"

Thanks for your assistance ! ! !

Regards,
Marc

I am giving a short "report", when there is new version out and I have tested it.

Nice weekend @y'all

Regards,
Marc

Problem still persists with commit e9b66.

Thanks for the support!

Regards,
Marc

Commit 1ba82 did change something. It transferred the VDI but then fails with the VDI_IN_USE on that particular machine.

Regards,
Marc

The problem still persists with commit e376a.

After installation of updates to XenOrchestra I reboot the VM. Still no backup on this one VM possible.

For now I have created a separate backup job which seems to be working.

Regards,
Marc

I have restarted XO as well as my NAS several times since Saturday.

Still no change.

Regards,
Marc

Hi @pierrebrunet.

Thanks for the tip.

Didn't help, unfortunately. Same error message regarding VDI_IN_USE.

Regards,
Marc

Hi @DustinB

The VM could be backed up successfully with the same warning about the "disk parent":

The backup log:

{
  "data": {
    "mode": "delta",
    "reportWhen": "never"
  },
  "id": "1780940083480",
  "jobId": "8326600e-9863-4afa-b724-ae493f564ec8",
  "jobName": "ITServices-Detla-Test",
  "message": "backup",
  "scheduleId": "98f60867-3ac9-4ec5-b0fc-c3fe5520dc1b",
  "start": 1780940083480,
  "status": "success",
  "tasks": [
    {
      "id": "0mq5hqsy6-9uqj9yfb22",
      "start": 1780940085774,
      "status": "success",
      "tasks": [
        {
          "id": "0mq5hqsyx-i5pdr4zkson",
          "start": 1780940085801,
          "status": "success",
          "warnings": [
            {
              "data": {
                "path": "/xo-vm-backups/011114a9-b622-92eb-581f-36f961efe622/vdis/21bbca2a-59ad-4fa2-bb73-f60c1e9216e7/63a73be5-96ff-4c25-b7dd-c93284719916/20260608T150007Z.vhd",
                "error": {}
              },
              "message": "failed to read disk parent info"
            }
          ],
          "end": 1780940085910,
          "result": {
            "merge": false,
            "size": 0
          },
          "message": "clean-vm"
        },
        {
          "id": "0mq5hqtyu-9l484fbage",
          "start": 1780940087094,
          "status": "success",
          "end": 1780940087947,
          "result": "396960d5-93e9-670e-e8b5-345283148c0f",
          "message": "snapshot"
        },
        {
          "id": "0mq5hqumk-7yfetdkltc2",
          "start": 1780940087948,
          "status": "success",
          "tasks": [
            {
              "id": "0mq5hqvn3-wfuuk0sz1mi",
              "start": 1780940089263,
              "status": "success",
              "end": 1780940089285,
              "result": {
                "size": 104448
              },
              "message": "transfer",
              "data": {
                "progress": 100
              }
            },
            {
              "id": "0mq5hr0dj-1l495zk6iys",
              "start": 1780940095399,
              "status": "success",
              "warnings": [
                {
                  "data": {
                    "path": "/xo-vm-backups/011114a9-b622-92eb-581f-36f961efe622/vdis/21bbca2a-59ad-4fa2-bb73-f60c1e9216e7/63a73be5-96ff-4c25-b7dd-c93284719916/20260608T150007Z.vhd",
                    "error": {}
                  },
                  "message": "failed to read disk parent info"
                }
              ],
              "end": 1780940095573,
              "result": {
                "merge": true,
                "size": 0
              },
              "message": "clean-vm"
            }
          ],
          "end": 1780940095590,
          "message": "export",
          "data": {
            "id": "442a4fc2-70ff-474d-aae9-88d0249ef5f2",
            "isFull": false,
            "type": "remote"
          }
        }
      ],
      "end": 1780940095590,
      "message": "backup VM",
      "data": {
        "id": "011114a9-b622-92eb-581f-36f961efe622",
        "type": "VM",
        "name_label": "ITServices",
        "progress": 0
      }
    }
  ],
  "end": 1780940095591,
  "infos": [
    {
      "data": {
        "vms": [
          "011114a9-b622-92eb-581f-36f961efe622"
        ]
      },
      "message": "vms"
    }
  ]
}

I am using "smart mode" for backup jobs. The standalone job went through with and without "smart mode".

Removing the tag from the VM in question and adding it again did not help. I have also deleted the snapshot linked to the backup job and retried, with no change in behavior.

The VM is shutdown and I only turn it on when I need to. During backup it is usually not running.

Thanks again.

Regards,
Marc