Good catch Dan and good decision @McHenry Even if you don't run VM, dom0 is used for VM transfer/backup/replication, so having 4GiB or RAM is a lot better in your case

New job, try pool.rollingUpdate

@McHenry like @olivierlambert said, keep in mind that a VM with 16 CPUs will be less available than a VM with 4 vCPUs, because it's easier to have 4 vCPUs ready to work than 16 simultaneously beware of this graph, it only graph the first 16 vCPU, but you can have more working ! the visual widget is failing you. think of topology too : if you have two sockets, you can have a topology of 2 sockets with 4 cores for a 8 vCPU VM. If you have only one socket, try to keep the topology to "1 socket xx cores" for your VMs, performance wise.

@olivierlambert Here's the new model. We've tried a few combinations and I think with TrueNAS shared storage this will now work well. [image: 1759787234216-f78178c0-3330-4233-8f9b-debc3c61a3e9-image.png]

@flakpyro All this complexity makes me question the advantages of having all hosts in the same pool.

@Danp Thank you.

Question for @florent

It's better to have it to get handy options like IP addresses displayed and so on.

@dinhngtu Thank you so much. If you want me I'll be at the pub.

Hello, I am asking XO team.

That's great, those are companies with 100% backup dedicated products We cannot be everywhere and we have to prioritize on what most people expect. Recovery capabilities on a second site is like one of the most needed feature, that's why we did CR. From a technical stand point, when a VM is replicated, it's on another SR and XO doesn't have any direct access to the SR to mount it. IDK how VEEAM is doing, likely accessing the SR or similar (at least not on XCP-ng )

@McHenry xo-cli backupNg.getLogs --json limit='json:500' should work ( the command line parameter are considered as string )

@olivierlambert Hyper-V has the concept of Dynamic memory as documented below. This allows a startup mem value to be specified and something similar could be used for health checks as this is only needed for the network to connect then them VM gets killed. [image: 1745470452383-f746e366-9f3a-4d78-a6d7-219c8faac555-image.png]

Have you read the doc first? https://docs.xcp-ng.org/xostor/ This gives a nice overview on how it works

This is not a backup but a replication

Hi, If you have support, you should create a ticket asking for the feature if you need. We don't have much request for that, but if nobody ask, it will never happen by chance If you don't, you can still open an issue on our XCP-ng repo to ask for it, at least we'll have a trace of the request

@DustinB Emergency Reset Worked. ty

@Danp have now

@DustinB Thanks Dustin. This is exactly our goal setup. Thinking further, as XO/XOA could be hosted on either host it would make sense to host this on the DR host.