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
@acebmxer NFS remotes on the DS1819+ ?
we have iSCSI SR (25Gb mellanox 6 PIFs on hosts to 25Gb MSA2062 SAN dual controller)
our remotes are iSCSI os mounted volumes on MSA SANs, presented as S3 (minio VMs)
using XO PROXIES to offload backups from XOA
we max out a 150/200Mb/s during backups 
but we are on VHD VDIs, asking myself if the added backup performance you present could be due to QCOW2 format on source SR ?
will have to try VDIs on such SR to see the diff
@acebmxer so, NBD it was...
holy molly, you have some good network performance !
what kind of SR at source ? and remote at destination ?
what about the PIFs ?
@acebmxer bottom of POOL advanced tab, is BACKUP NETWORK selected on the NBD enabled network accessible by both hosts and XOA ?
@acebmxer I have a new case of managing to force the fell back to full error...
i'll create a new topic for this
in the time being, if you can, do a toolstack restart on your pool when no tasks is ongoing
your backups with NBD could be better (spoiler alert : iptables rules... )
Thanks.
The old snapshots are being removed as the total never increases beyond 16, so when a new snapshot is added, the old one is removed.
immediatly removed, yes, but then Garbage collection takes place.
and perhaps with 19x16 GC to process it can't be done in one hour, and then next CR is launched, etc etc...
@florent was finally able to read the pull
/clap ! the fix seems totally legit and consistant with XOA ram ramping up !
when will this be officially published ? 
so we can disable daily reboot of XOA & XO PROXies
@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.
