@AlexanderK

Clonezilla is my go to for doing that. I have a tutorial where I should how to migrate from Virtualbox to XCP-NG here:
https://youtu.be/wSTk9BLwF5k

@olivierlambert

I work with enterprise companies and they NEED those reminders to let them know they should be using the supported version. I don't really see them as annoying at all.

@bullerwins

It's a wonderful feature, you can have customized filters for VM, storage, Templates, and Pools. Combine that with using lots of tags and it makes larger deployments very manageable.

@CodeMercenary

Under the xo-vm-backups directory is a series of directories named with UUID's that contain everything that belongs to a particular VM's backup. As long as you keep each directory and all the contents nested within it you will be able to restore that VM.

@jasonnix

That is enough to get it working and fine for most homelab environments.

@MichaelCropper
I recently did a video tutorial on how XCP-NG virtual machine dynamic memory management and over allocation works.

https://youtu.be/Lsi2-hAoKSE

@abudef
XO will utilize the existing VM disk or snapshot as a base, restoring only the differential data to a new disk saving time. More details are in this blog post
https://xen-orchestra.com/blog/xen-orchestra-5-89/

@abudef
Yes, as far as I know the only way to restore a VM but keep all the GUIDs the same is to roll back a snapshot.

@starmood For each VM backup run inside of Xen Orchestra it backs up not just the VHD but everything that is needed to restore that VM to any other XCP-ng host. So in a complete loss situation you can load a new XCP-ng Host, setup Xen Orchestra, point the new Xen Orchestra to those backups and restore any of the VM's with all their settings.

The metadata backup of XCP-ng is just that, the metadata of the system and it's not granular. It's good to have because all the things like network setting and what VM's are on the hosts will be there, but the VM backups to me are the most important.

I have a tutorial covering how the backups work, it's from a bit over a year ago and there are EVEN MORE features now and I will be doing a new video this year to cover that.

https://youtu.be/weVoKm8kDb4?si=1z6IDqwnK1cxEGjm

I also have a tutorial on how you can also automate the backup validation process
https://youtu.be/A0HTRF3dhQE?si=gZLXQUqLJmDkIQs6

@Matteo

If the storage type you have the VM is thick provisioned it will take up more space. Use a thin provisioned storage for better storage efficiency
https://xcp-ng.org/docs/storage.html#storage-types

If you choose 2 storage destinations it will copy to each of them at the same time.

@abudef
XO will utilize the existing VM disk or snapshot as a base, restoring only the differential data to a new disk saving time. More details are in this blog post
https://xen-orchestra.com/blog/xen-orchestra-5-89/

@abudef
Yes, as far as I know the only way to restore a VM but keep all the GUIDs the same is to roll back a snapshot.

@abudef

It's a new VM so it get's a new GUID. Why would you want it to have the same one? Also if you keep the snapshot when doing a delta backup you can roll that VM back and keep it's GUID.

@thomas-wood "Remotes" are for XO backups and SR are for VM Storage. Once you add a SR to a pool it's available to all hosts. Also, all hosts should be able to access the IP of the NFS server before setting that up.

I have a video explaining storage in XCP-ng here:
https://youtu.be/xTo1F3LUhbE?si=QHYkABgElsEVOj6H

@thomas-wood Yes, go with TrueNAS Scale. Also, TrueNAS Scale will be called TrueNAS Community with the next version 25 release.

Why are you doing this with TrueNAS Core? It has reached end of life.

@djp I am not really sure what else besides migration traffic passes over that .

@djp If you assign IP's to the hosts in the same subnet range for a given network it should show up in that list.

@kagbasi-ngc

If you update the XOA it will not change the Memory or CPU setting of VM.

@kagbasi-ngc
Yes, but of course speed varies by setup. I have 10G in my lab since it's so common and many of our clients are running 25G setups and bonded to 50G.

You can add more CPU if you need more processing power for XOA for running more concurrent backups. If XOA were to ship with a high memory and or CPU setting by default it would not work on some setup that don't have the resources. Defaults work fine but for people who need more there are options.