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.
@Bastien-Nollet okay i'll do that tonight and will report back
@Bastien-Nollet 100% of our backup jobs are done by proxy
we offload that of main XOA that is purely for administration/management
@User-cxs si ici :
tu DISABLE le serveur. tu nous confirme que c'est "comme" le probleme que tu constates ? un XOA tout vide en page d'accueil ?
tu re ENABLE, et ça reviens ok ?
tu n'as pas de probleme réseau / micro coupures / host distant au XOA (ipsec/openvpn?) ?
la déco/reco que tu as me fait penser a un simple probleme réseau (si ça reviens tout seul et aucun autre impact...)
@User-cxs tu peux aller voir dans SETTINGS / SERVERS ?
on dirait que tous les hotes master sont disable/disconnect
ou alors tu as un toolstack restart inopiné...
@anthoineb wow great news ! still impacted by this issue
This may not be best practice.
in a two hosts pool, if your replicated VMs live on the Master, and it's gone, you won't be able to start the replicated VMs
you will first need to transition slave to master
indeed CR is better to another pool
@Dezerd you just have to start-copy the Replica VM
it permits the original job to keep replicating on the VM.
there is no failover/failback mecanism AFAIK
if you work on replica started VM, you will have to put up in place a replica going to original hosts
@User-cxs it is possible as long as your OS accepts it.
must be planned in the advanced settings of your VM.
Can be hotplug
If your CPU limits are 2/8, you can hotplug 6 more vcpus
@florent ho nice
we had as many "VMs with a timestamp in the name" as number of REPLICAs, and multiple snapshot on source VM
now we have "one Replica VM with multiple snapshots" ? Veeam-replica-style...
do multiple snapshots persists on source VM too ?
if it's true, that's nice on the concept.
but when your replica is over lvmoiscsi 
not so nice
ps : i didnt upgrade to last XOA/XCP patchs yet
@florent Florent, I could see the benefits of unified VM name, but could you at least push the timestamp in a note on the VM ?
it is important to know wich timestamp a replica VM is, in order to choose failover option wisely
@nikade Hey Nikade,
Did you try to create a new job that will do a new chain ? Just for test.