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

@Matteo
You can use a SAN shared storage that is thin provisioned such as NFS.

@DustinB said in Delta backup questions:

As a discrete backup that is saved to each location individually.

Yes, that is a more accurate statement.

Also, there is an option for doing Mirrored Backups:
https://xen-orchestra.com/docs/mirror_backup.html#mirror-backups

@Lulina

The VM created for the health check is deleted after boot confirmation is achieved by seeing the Xen tools.

@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
I only did that in my video to make it easier to show how things work with XCP-ng hosts, I don't think the VM's would work inside the nested systems.

@nikade
Something to consider is that due to the way XCP-ng isolates for each disk for each VM for better security there can be some performance issues. But because it's per VM (unless your use case is to only running a single VM) this is less of an issues as most people run many VM's.

@paulorrockgit

This is clever!

@djingo
My syslog stopped working (I think after one o the updates) and this bug still exists. If you trying removing it form the Pool or individual hosts in the Pool via XO it will not let you have it as blank. If you ssh in and use xsconsole you can remove the syslog server and but it will not let you specify a port. But once it has been removed from xsconsole you can go back into XO and add in the syslogserver along with a non-default port such as

192.168.2.7:1521

and it will work.

@OskarNTT

For HA to work properly you need 3 hosts.

https://xcp-ng.org/docs/ha.html#introduction

@jasonnix

If you are going to do it manually then choose whatever you want, but /tmp might not make much sense to put something important.

@jasonnix

use an account that is in the sudo list.

@jasonnix

I have. a tutorial here on how to build from sources using https://github.com/ronivay/XenOrchestraInstallerUpdater which can be done using a sudo user.

https://youtu.be/fuS7tSOxcSo

@jasonnix

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

@john-c said in Backup Design and or Feature for Managed IT Services:

Could the tags play a part here

Yes, tagging each pool, storage, VM and Host with a customer name would make organizing this easy to do.

For the use case where an internal IT team for a single company is replacing VMWare with XCP-NG/XO having the integrated backup system it is great selling point.

On the other side, as a Managed Service Provider that has to manage many separate companies there is a challenge with that process and I am look for some suggestion and guidance that may lead to some feature requests.

The challenge is figuring out the best way to use XO for many clients. My idea is connecting all of our clients to an XOA instance we host so we have visibility in their environments to make sure they are patched and the backups are being managed.

Central Design Idea

• Have one XOA instance that we host in our infrastructure
• Create VPN to each client
• Have XOA Proxy at each client to handle local backups that go to on site client NAS
• Use S3 option to bring all backups back to our infrastructure

Challenges with this design
The ideal way for this to work would like the tools we currently use for VMWare management, which are Auvik for monitoring the stats and Veeam for handling backups. Both of those tools create tickets in our system to alert us of problems.

Besides going into the XOA interface everyday or getting all notices sent via email I am not aware of any way to manage the success or failure of the backups for all clients. Maybe there is a way to do this that I am not aware of via the API? Does this sound like a good way to handle client management?

We have some developers and are willing to sponsor writing open source code to get these features done, but I first want to make sure I am on the right track in terms of design, or if each client should have their own XOA instance.

@Niko1

I am not using and PCI pass through but I have three of these Ryzen systems and they have working great for over a year.

Parts list here: https://kit.co/lawrencesystems/ryzen-9-xcp-ng-virtualization-server-build-with-25gb

Video on the setup here:
https://youtu.be/AbzKv_3x5S4?si=wI8OCd3-YMDl4jyS