@olivierlambert I agree, ping @thomas-dkmt

There's many ways: no backup whatsoever. You will be able to restore your previous backups with a fresh XOA anyway (but you'll have to recreate the backup jobs and local users) metadata backup: very fast to backup and restore on a fresh XOA, probably the easiest way. With XOA, you also have Cloud enabled backup where you metadata will be saved directly on your Vates account (with a password and encrypted) "regular" backup on your XOA (full, incremental, replication…)

Thanks, In a perfect world, self-service users should be able to manage ACLs on their VMs and show backup tab on VM.

@rporter and @still_at_work There's actually a super useful guide here. If you have any questions feel free to post back here and I'll try to help.

@CJ yum update from 8.3 beta to 8.3 will be possible, but I still recommend using the ISO. In a perfect world, yum update would give you exactly the same result, but in reality there are always corner cases where files or packages are left behind (we have no sane way to tell yum/rpm to remove an installed RPM, unless making another RPM obsolete it and thus make it impossible to reinstall later if someone needs it for a good reason).

@olivierlambert OK thanks!

Yes indeed, if you are not passing a static IP in the template, Cloud init will wait to get an IP for few minutes before continuing to boot

@olivierlambert Thank you very much Olivier, this is exactly what I want to do!

@still_at_work Personally would say AMD, almost all XCP-ng servers I manage are AMD based and have been excellent so far. Usually a better value and better overall performance and their high core counts are great for virtualization unless you specifically need something that is faster single threaded. I have 3 hosts in my lab, all Threadripper (so baby EPYC) and they've been rock solid as well.