Assumming these hypothetical circumstances:
- Standalone PVE server (no HA/cluster)
- rpool crashed, server won't boot, PVE can't launch.
- Must build new standalone PVE from scratch
- Have recent full backups of each VM hosted on the failed PVE
I assuming one will be missing (and requiring) the configurations of the VM's themselves? (i.e. disks, nics/virtual macs, other settings, etc.)
Is there some place these are kept within the system so that they could be backed up and re-imported into a new/replacement PVE prior to restoration of VM(s) from backup?
Other than the VM settings would there be anything else to consider in this situation?
Maybe Proxmox team at some point would consider dumping VM settings to restorable file with/in backup directoy at same time? Though I understand cluster/HA would resolve this, but because of MS licensing, it's an expensive PITA to use PVE w/Windows.
- Standalone PVE server (no HA/cluster)
- rpool crashed, server won't boot, PVE can't launch.
- Must build new standalone PVE from scratch
- Have recent full backups of each VM hosted on the failed PVE
I assuming one will be missing (and requiring) the configurations of the VM's themselves? (i.e. disks, nics/virtual macs, other settings, etc.)
Is there some place these are kept within the system so that they could be backed up and re-imported into a new/replacement PVE prior to restoration of VM(s) from backup?
Other than the VM settings would there be anything else to consider in this situation?
Maybe Proxmox team at some point would consider dumping VM settings to restorable file with/in backup directoy at same time? Though I understand cluster/HA would resolve this, but because of MS licensing, it's an expensive PITA to use PVE w/Windows.