XO Backup Error: VDI_IN_USE(OpaqueRef:.., destroy)

itservices

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

itservices

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

Regards,
Marc

itservices

Problem still persists with commit e9b66.

Thanks for the support!

Regards,
Marc

pierrebrunet

@itservices Hi,
We did not forget you, working on it!

itservices

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

Nice weekend @y'all

Regards,
Marc

itservices

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

pierrebrunet

@itservices Can you check your health dashboard where you should see " Unhealthy VDIs" ? If there are too many VDI in it, they need to be coalesced before restarting a backup.

itservices

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

itservices

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

itservices

With commit caa17 the transfer did not happen again and fails the with the known message.

Regards,
Marc