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.

@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