Where is the doc for these ? edit ok right here https://github.com/vatesfr/xen-orchestra/tree/master/%40xen-orchestra/immutable-backups , with V**m there is an option for immutability when you add the S3 bucket directly so its look like its only a flag sent at bucket creation and using the versionning/compliance feature

@florent Is there somewhere we could discuss therse not on public forum....Thanks !

@florent So if proxy lost contact with XOA , all backup will still failed and all backup status are losted ? I would be nice if proxy become full autonomous , so this way you could upgrade XOA , restart it and all backup job would run themselve and report back to main console

Hi , after some search to find a backup software we found SEP Backup Software and I read some interesting doc into their wiki , I would like to know if this is still de case with 8.2.1 LTS

As XCP-ng is based on Citrix Hypervisor that has removed support for VSS and quiesced snapshots in Citrix Hypervisor ≥ 8.1 and in version ≥ 9.0.x.x drivers, the following applies: To continue using the quiesced snapshot feature with Windows VMs hosted on XCP-ng 8.0 and earlier, keep your current 8.2.x.x version of the Windows I/O drivers and do not update to the 9.0.x.x drivers. For more information, see XCP ng 8.1 Release Notes and Citrix Hypervisor 8.1 Deprecations and removals.

Is this correct ? ( windows update push citrix tools 9.xx )

Some news ?

@julien-f , vm not found , no xapi associated to

How we could be assure than everything is correctly backup ? Just received the XOA news with experimental VEEAM support , we will try these , we need something robust with advanced feature ( object storage , immutable , backup validation , dedup ) , with all encryption/ransom we need solid and functionnal DR plan with fast recovery and we are also checking HyperV

@julien-f , each time XO Proxy losted connection with XOA we received a failed backup but you are saying than backup will be done ? Humm we need to do some test but how we will know than backup is successfull ?

Hi , its looked like if the proxy is losing comm with XOA and there is some running job , they are all stucked and everything need to be re-done from the beginning, right ? So to be clear the proxy could not operate alone right ? I understand than there is no UI on the proxy but my vision was XOA is only there to manage it remotely and once you change/send config the proxy is running themself , we try it at some site but the product is pinging so much at XOA than even with alot of ressources XOA is completely overwhelmed by all our jobs + proxy's management , for the record our XOA is currently with 16GB and 16cpu on a 7402 epyc

Same issue there , we have around 125VMs and this is becoming a real problem , sometime a REP should used no more than 10GB and this is causing big transfer and rep delay, we just tried the xo-cr-seed and once we restart the backup ( 2 days from initial seed snapshot ) the transfer initiated a 12 hours backup delay so this is almost useless for remote DR site