Hi,
It happens, more than we would like, that a server/disc/controller crashes and that the relevant proxmox node becomes marked as offline. The problem is that containers and vms hosted on this node become irrelevant numbers. Add to this, that when creating new VMs/containers or restoring ones from backups, freed numbers of previously destroyed VMs/containers are recycled, so we end up not knowing which VMs/containers where running on that crashed node; even on the backup jobs these VMs/containers become unknown.
Does anyone know of a method for making an up to date global VMs/containers catalogue that survives nodes crashes.
I had to download /etc/hosts from pbs backups to try to discover node names.
TIA
It happens, more than we would like, that a server/disc/controller crashes and that the relevant proxmox node becomes marked as offline. The problem is that containers and vms hosted on this node become irrelevant numbers. Add to this, that when creating new VMs/containers or restoring ones from backups, freed numbers of previously destroyed VMs/containers are recycled, so we end up not knowing which VMs/containers where running on that crashed node; even on the backup jobs these VMs/containers become unknown.
Does anyone know of a method for making an up to date global VMs/containers catalogue that survives nodes crashes.
I had to download /etc/hosts from pbs backups to try to discover node names.
TIA