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
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 ?
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
@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
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.
@simonp patched tonight, a job who took 3 hours yesterday took only 1 tonight.
so, big improvment !
need to re up concurrency to 2 or 4 on some jobs to see if I can squeeze more time on the backup window
hey,
Could be of some interest for french speakers and why not others in the forums :
https://go.veeam.com/webinar-technical-cloud-club-france
@McHenry could you screen the health page ?
where we could see the chain length
@McHenry I dont think more than 3 snapshots triggers an error, just tested on one VM 
it is not recommended for "in production" VMs, but for a CR destination, it's OK (as you would need to start a copy anyway)
your problem, failing CR jobs is probably due to garbage collection not finishing in the one hour timeframe when chain is long.
@simonp patched tonight, a job who took 3 hours yesterday took only 1 tonight.
so, big improvment !
need to re up concurrency to 2 or 4 on some jobs to see if I can squeeze more time on the backup window
perhaps "in the context of a proceeding RPU, do not start halted VMs" ?
or "boot only halted VMs that have HA enabled" ?
but I can imagine corner cases where this is not wanted.
some chicken & egg problem.
@stormi indeed.
but the host restarting is by design empty of all VMs because of evacuate process
the stopped VMs are on other hosts. so strange to see them booting when restarted host is coming online.
ps : as I wrote it, I understood my "error". halted VMs are on no host at all, just attached to the pool.
I did verify and yes
odd ha-reboot-vm-on-internal-shutdown ( RW): true
it is enabled on our Pool. but no HA
ha-enabled ( RO): false
@stormi no, we do not use HA, it's disabled on the POOL and on the VMs
@olivierlambert having done a RPU yesterday on 3 hosts, I still have the "bug" where some VMs with "auto start" switched ON, but halted on purpose, reboot when a host is rebooted.
we do stop some VMs during RPU to lessen the migrate times, but at every host reboot, they DO START UP
annoying. not critical, but annoying.