@florent yes I can try with XO from source to latest
let me restore the VM and launch a DR with XO from source and i'll report back

source host :

xe host-param-list uuid=161be695-e1f9-4271-b581-27b716fde9a5 |grep xapi

software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; build_number: cloud; git_id: 0; hostname: localhost; date: 20250909T12:59:54Z; dbv: 0.0.1; xapi: 25.6; xapi_build: 25.6.0; xen: 4.17.5-15; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.786

DR target host :

xe host-param-list uuid=e604c3bf-373c-489b-b191-edecbabec43f |grep xapi

software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; build_number: cloud; git_id: 0; hostname: localhost; date: 20250909T12:59:54Z; dbv: 0.0.1; xapi: 25.6; xapi_build: 25.6.0; xen: 4.17.5-15; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.786

tried to delete the VM, restore it, same result

tried to get the job done by an XO PROXY instead of XOA, same result

3 VMs have been deployed from the same Hub Template Ubuntu 24.04 at the same time.

weird.

@florent this is where it's strange, all my 7 hosts were installed the same day, with the same patches...
all 3 VMs were deployed the same day/way too

why are 2 OK and not the third ?

indeed CR is working, but DR is hiding something from me

Hi,

XCP 8.3, XOA 5.113.2 here

a DR job, with 3 VMs, 2 are OK, one will not pass... And I dont understand why, first time I see this error

   "message": "(intermediate value) is not iterable",
        "name": "TypeError",
        "stack": "TypeError: (intermediate value) is not iterable\n    at Xapi.import (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/xapi/vm.mjs:610:21)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/backups/_runners/_writers/FullXapiWriter.mjs:56:21"

any idea anyone ?
or @bastien-nollet @florent

there is free space on the destination SR (iSCSI SR)

@olivierlambert nice, better than megathreads ! added my first TAG demand on it

about these KEY backups, I think perhaps LTR got in the way @florent @bastien-nollet

still no way of knowing WHEN a weekly/monthly backup is happening ?

@flakpyro indeed seems related.

I also have this bug :

on some VMs all jobs do KEY points, but in the backup logs they are indeed DELTA

you can see as mere Megabytes are transfered that it's a delta backup... but point is presented as KEY

here is the log :

Hi,

Latest XOA, with fully patched XCP 8.3 here.

I'm fiddling around again with NBD+CBT in backup jobs (was avoiding CBT for a time, to reliably control my backups and avoid unnecessary KEY points) in the context of THICK SRs to spare some space.

I know that CBT is reset when migrating from one SR to another.

But here is what I encounter :

• VM has no CBT enabled on its VDIs, it is on a SHARED SR in a pool of 3 hosts
• backup option changed for NBD+CBT, was only NBD before
• CBT is enabled on the next run by the backup job, I get a delta (was expecting a FULL ?)
• next run, delta, as expected
• i migrate this VM on another HOST, without changing its SR
• CBT is immediatly disabled ? why ??
• next run of backup it tries a delta, but "fall back to a full" (normal as CBT has been disabled...), and do a KEY point on the remote
• next run is a delta as expected

does this mean if I do a rolling pool update or host maintenance that will move the all VMs around, all CBT will be disabled and I should expect a FALL BACK TO FULL on all my NBD+CBT enabled backup jobs ??!

why disabling CBT on a change of HOST and no move of SR ?

@denis.grilli really big news, I need to have XO STOR working
Thanks for your problems and support correting them

@olivierlambert so XO5 will have a quite long lifespan, as everything must be included in XO6 ?

@ph7 thank you for your tests

some Vates dev are lurking in these forums, they will probably stumble upon this post anytime soon

@ph7 that's it. I can't, and see the failed task logs I provided earlier.

I can restore a full VM, but not its files. Either Windows or different flavor of linuxes (debian, ubuntu, alma, ...) same problems.

I think something is wrong somewhere, but dont know where...

any idea anyone ?

halp needed

annnnnnnd it was as simple as converting date to milliseconds.

start:>1765209598000 end:<1765231198000

Hi,

what would be the syntax to filter logs by start-date / end-date ?
epoch timestamp ?

any idea or how-to ?

@Forza you will have to switch to LATEST to profit from end month release
STABLE is one version behind LATEST

both are production ready.

@bazzacad first time I see orange VDIs in this view

@paco seems to be the 10Mb cloudconfig drive leftover after template deployement

you could delete it, if it is not in use anymore (you forgot it ?)

beware do not delete anything before being sure what you are deleting.

on another simpler install (One host, one XOA, no proxy, SMB remote in same lan not an S3 remote), XOA 5.112.1

same problem !

I think something has been broken along the way @bastien-nollet @florent

granular file restore is important for us, otherwise we have to get Veeam Agent backup instead of XO Backup