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
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 
is there anywhere where we can check the backlog / work in progress / to be done on XO6 ?
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.
@Bastien-Nollet okay i'll do that tonight and will report back
@Bastien-Nollet said in backup mail report says INTERRUPTED but it's not ?:
file packages/xo-server-backup-reports/dist/index.js by a
modification done, will give feedback
@dinhngtu tried on a Windows Server 2025 VM, UEFI BIOS
working well, no reboot needed
@florent I did healthchecks one month or two ago.. I do not remember precisely
but I didn't have this bug.
so either specific to OP installation, or there is a regression somewhere
@Greg_E i think protection is doing its job. do not delete.
but in case of healthcheck, the process should bypass that for the restored VM
thoughts @bastien-nollet @florent ?
@olivierlambert okay, understood.
it is small minor cosmetic problem as of now.
need to get you an access to our internal developped app, to show you the potential of sub-xoas ^^'
almost out of alpha phase
hi,
We added pools/hosts on main XOA with XO PROXY httpUrl
we try to get all our clients onpremise pools&hosts in our "MSP-like" central XOA
host are seen not licensed

and so are the proxies

but on the remote sites, there is a licence & pro support in the remote XOA
I get it, on the central XOA is not present the licence of the others XOA onprem. so we get this error.
Would it be possible to "fetch" the licence information when attaching these remote pools/hosts ?
@john.c said in backup mail report says INTERRUPTED but it's not ?:
Are you using NodeJS 22 or 24 for your instance of XO?
here is the node version on our problematic XOA

this XOA do NOT manage backup jobs, totally offloaded to XO PROXIES
XOA PROXies :
[06:18 04] xoa@XOA-PROXY01:~$ node -v
v20.18.3
and XO CE :
root@fallback-XOA:~# node -v
v24.13.0
memory problems arise on our XOA
we have a spare XO CE deployed by ronivay script on ubuntu VM that we use only as a spare when main XOA is upgrading/rebooting
same pools/hosts attached, quite a read only XO
totally different behavior


@florent said in backup mail report says INTERRUPTED but it's not ?:
@Pilow We pushed a lot of memory fixes to master, would it be possible to test it ?
how so ? I stop my reboot everyday task and check if RAM is still crawling to 8Gb ?
@randyrue on our side, we do not use custom fields, but TAGs.
working well. depends on the number of custom fields you manage, and perhaps not usable because you need field:value ?
but nested tags could do the trick : field=value
