It's up to you to do whatever you need with the VM copy. Clone the replicated VM, remove the NICs (for example) and boot it.

Yes, the default timeout for XAPI tasks is 24 hours. This can be modified as explained in the documentation -- https://docs.xcp-ng.org/management/manage-locally/api/#24h-task-timeout

Your backup won't be affected if the VM is rebooted while the backup is running.

Ping @florent

Found this...

https://xcp-ng.org/forum/topic/3553/creating-schedules-to-run-on-specific-days

@olivierlambert

We have successfully installed using:

rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/7/x86_64/zabbix-release-latest.el7.noarch.rpm yum install zabbix-agent2 zabbix-agent2-plugin-* --enablerepo=base,updates

@florent

What are your thoughts on my last three questions please.

@McHenry Look at this post: VM limits - CPU Limits

@Andrew

Got it. So the DR host may have fewer resources than the production host, which would work for a failure of one or two VMs but not for a total failure of the production host whereby all VMs need to run on the DR host.

Is it only RAM that is a consideration between hosts? Meaning if my production host has 16 vCPUs and my DR host only has 8 vCPUs can I still set the VM to use 16 vCPUs and it will work on both hosts?

@McHenry Yes, XCP sees and uses all threads (8 core + SMT x2 threads = 16 logical cores). So you can assign all of them to a VM as long as the VM can use them.

XO shows 16 "cores" (total threads) and 1 socket. It also shows hyperthreading is enabled. XCP/XO does not differentiate between cores, threads, E-Cores or P-Cores.....a thread is an assignable core resource.

You can assign 16 logical vCPU that includes real cores and SMT threads.

Some programs do not work well with hyperthreading in a VM environment. So you may wish to disable SMT depending on the workload.

Is it PV, HVM or a PVHVM VM?
Health Check can't work on HVM because there are no tools.

@McHenry @nick-lloyd With todays release of Xen Orchestra (XOA) version 5.100 there's now support for custom ACLs based around tags. These will prove really useful when your setting up the XOA with its ACL for your clients to access self service, while ensuring that they can't access the other's pools and VMs etc.

@McHenry Base copies are not copy per say but a base of a VDI chain.

XO coalesce

Here you can see that A and B are base copies for the snapshots C and E while D is the active VDI.
You can find more info on this page: https://docs.xcp-ng.org/storage/#-coalesce

That's why warm is magical: it's a lot less risky while providing a reasonable availability 🙂

@McHenry +1. Never found how to do it....

Just going to XO / Home / Pools / pool-1 and pressing "Add hosts" button, selecting host-2 worked OK this time. So no detaching host from a pool and attaching to new pool ... just a button 🙂

@BenjiReis

Got it, thank you.