just to #brag

Deploy of worker is okay (one big rocky linux with default settings 6vcpu, 6Gb RAM, 100Gb vdi)

first backup is fine, with decent speed ! (to a xcp hosted S3 minio)

will keep testing

Hey all,

We are proud of our new setup, full XCPng hosting solution we racked in a datacenter today.
This is the production node, tomorrow i'll post the replica node !

XCPng 8.3, HPE hardware obviously, and we are preparing full automation of clients by API (from switch vlans to firewall public IP, and automatic VM deployment).

This needs a sticker "Vates Inside" #vent

@sluflyer06 and I wish HPE would be added too

I did stick to version: 1 in my working configuration

Had to rename my "Ethernet 2" nic name to Ethernet2 without the space

You have to put the exact template nic name for this to work.

@MajorP93 throw in multiple garbage collections during snap/desnap of backups on a XOSTOR SR, and these SR scans really get in the way

Hi,

Smart backups are wonderful to manage smart selection of VMs to be backuped.

When we browse the RESTORE section, would be cool to get the TAGs back visually, and possibility to filter them
I'd like to get "all VMs restorable with this particular TAG" type of filter, hope i'm clear.

Perhaps something to add to XO6 ?

Could we have a way to know wich backup is part of LTR ?
In veeam B&R, when doing LTR/GFS, there is a letter like W(weekly) M(monthly) Y(yearly)to signal the fact in the UI

That's pure cosmectics indeed, but practical.

@Forza I didn't try, as my default Graylog Input was UDP and worked with the hosts...

But guys, that was it. In TCP mode, it's working. Rapidly set up a TCP input, and voila.

is there anywhere where we can check the backlog / work in progress / to be done on XO6 ?

@MK.ultra don't think so

it's working without for me.

on the source VM :

• I tried to switch to another network and re put the good network to no avail
• I tried to put the network mentionned in the error (UUID that is not the good one), to no avail
• I deleted the VIF, recreated it with the good network for this VM

and booom, DR is okay ! that was not a XAPI problem

so, there was a problem with this VM VIF... and error message in XO6 permitted to pin point it

thanks for the advice @florent !

@florent

here is the errot in XO6
this UUID of network is NOT the one on the source VM...

how is it possible ?

@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 :