@Greg_E "if that host crashes" -- that's the problem. When the host is gone, VMs are gone. Not colored in red 'we are gone', there are none of them.

There is no problem running XO itself on other host.

The question is not how to keep VMs backed -- they are.

But right now, when host X is gone and its VMs are replicated to hosts Y and Z, how can i quickly see that VMs A,B,C and D are gone and E, F, G, etc are up? No way, because X is gone and its VMs gone too.

I have to monitor them via Zabbix to see if they are gone.

But syncing hundreds of VMs with Zabbix is tiresome, it's a lot of manual work.

@olivierlambert Cool. Waiting for that feature

Suppose I have a server with VMs replicated to 3 other different servers (weaker than the main one). Then the main server goes down. I need to assess quickly which copies I should start first. How do I quickly check all the VMs that went down? Some are not important, some are... Without a central list of VMs with their status, it's much trickier.

@olivierlambert I mean if the server goes down, all VMs that were running on that server disappear from XO. Yes, I can create manual entries to monitor them in Zabbix and I do, but for hundreds of VMs, that's a lot of manual work.

Basically, I'd like to see something like a table of VMs showing their status, availability of their replications on other servers, number of backups, etc.

Currently, I'm really falling behind with my Zabbix setup because there's too much manual work involved in tracking all VM IP addresses and other details (especially if some VMs are not easily accessible by IP!). There are no automated tools to properly view the status of each VM - not just up/down status, but comprehensive XO data.

The major drawback of Xen Orchestra is that if the server goes down, all of its VMs are gone too. No clean list of VMs in 'clean' state. Yes, there are backups—lots of them—and replications, but it understandig what's wrong is difficult. If you have hundreds of VMs, how do you track the state of individual VMs: which server each one runs on, which servers have replications, and where backups are stored?

@AtaxyaNetwork Yes, this worked. Thanks.

@AtaxyaNetwork Yes, I do.

I've added two new disks to the server and created md0 raid1 array, as described here: https://xcp-ng.org/docs/guides.html#software-raid-storage-repository. It works. Now I have to move VMs from the main, single disk of the server. But when I click migrate arrow on this server's vm, it does not show the same server as the destination, only other servers.

Yes, I can migrate VMs to another server and back, selecting new raid storage. But it's kinda awkward to haul hefty data between local disks via external machine...

@olivierlambert No, it does not. Still, sometimes badge with patches blink... funny.

@olivierlambert Well, after erasing that file it appears again with the same "check_update" contents.