@tuckertt

Not a direct answer to your question, but something to think about. I get that connecting XO to Active Directory is good for centralized identity management and offers rasier onboarding/offboarding, one password to rule them all. But the reality is that once AD is compromised, attackers can pivot straight into the virtualization layer — the crown jewels.

@coolsport00

Sounds like you have some issues either because you are changing the IP's after you setup the pool or you are having

I cover how to deal with host failures in this video:

Level Up Your XCP-ng & XO Knowledge: Tips for System Management & Recovering Hosts From Failure
https://youtu.be/WvXTq3adN08?si=ruaG2tMuC9iBSmTq

@coolsport00

Yes, always have all systems to full patch level before adding them to pools.

Also, I don't recommend using Xencenter just use XO.

For clarification the platform has been around and in use for a while. The Xen hypervisor was first released in 2003 then Citrix Xensever around 2007 with XO first being released in 2013. XO has been around since 2013 first to manage Citrix and then Vates released XCP-ng in 2017. XO Still works with both platforms.

@coolsport00

I have been using XO & XCP-ng for years now for many of our commercial clients and it's a very solid platform.
While there is a lot of good documentation for XO & XCP-ng first starting out with a new virtualization platform can be a steep learning curve which is why I have a series of videos that are designed to help people get started on the platform. Hope you find them helpful.

Your Complete Open Source Virtualization Guide For Getting Started With XCP-ng & Xen Orchestra
https://youtu.be/2wMmSm_ZeZ4?si=6RsiFiENct8fxurw

Level Up Your XCP-ng & XO Knowledge: Tips for System Management & Recovering Hosts From Failure
https://youtu.be/WvXTq3adN08?si=ruaG2tMuC9iBSmTq

@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.

@kagbasi-ngc
Yes, I put XOA on a 10G (or faster) connection and make sure it has enough resources to process the backups.

@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

@McHenry

I have a video breaking down how XCP-ng and XO work and at the 14:50 mark in my video here I break down how the XO Proxy works.

https://youtu.be/CEUFHudLO1g?si=UpoCWc6wCrK4iXFX

@jsox79 said in storage configurations are pretty disjointed:

reinitializing the hba storage

Are you trying to share the HBA storage from one host to the others?

@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.

@aqua-calc

I can confirm that a Synology works well as a backup "Remote" but as @olivierlambert said more details are needed to help.