Hi all,
I'm new to Proxmox and I fall in love with virtualization and Proxmox.
I'm using Proxmox on an HPE Proliant ML30 at home (knx, smartvisu, dns, ...) (--> lets call him pve1) With my old server running Debian and everythin installed on this OS, I sometimes had issues about stability, and when I was on a longer business trip and one of this "stability" issues occoured, the woman acceptance factor was drastically sinking.
This is why I got the new server and everything got much more stable now.
The new system runs much much more stabe and I had no issues in 3 months. Anyhow, I came up with the idea to also install proxmox on my old "server" together with Proxmox Backup (--> lets call this one pve2) with the folllowing requirements:
Requirement 1 and 2 are not to hard to realize I would say
The idea of Requirment 3 and 4 is basically a easy to start (for my wife) fallback if something happens to the main server.
But I do not know how to do Requirement 3 and 4. At the beginning I thought I could do this with a cluster, but there I would need a third machine as quorum. If I run a cluster out of 2 nodes and one is powered off, nothing is working at all.
Wouln't it be enough that pve1 always runs the VMs, no matter how many nodes are available. pve2 only runs the VMs if only 1 node is available (pve1 can not be reached)
Any idea how this could be realized?
I'm new to Proxmox and I fall in love with virtualization and Proxmox.
I'm using Proxmox on an HPE Proliant ML30 at home (knx, smartvisu, dns, ...) (--> lets call him pve1) With my old server running Debian and everythin installed on this OS, I sometimes had issues about stability, and when I was on a longer business trip and one of this "stability" issues occoured, the woman acceptance factor was drastically sinking.
This is why I got the new server and everything got much more stable now.
The new system runs much much more stabe and I had no issues in 3 months. Anyhow, I came up with the idea to also install proxmox on my old "server" together with Proxmox Backup (--> lets call this one pve2) with the folllowing requirements:
- pve2 shall not run 24/7 to avoid high electricity costs
- pve2 shall be powered up when needed for backup: pve2 wakes up (e.g. by timer at 2am) --> pve1 sends his backups to pve2 (e.g. 2:15am) --> pve2 turns off (e.g. by cron at 2:30)
- pve2 and pve1 shall synchronize their VMs if both are online
- pve2 shall start the VMs automatically if server is turned on manually by power button and pve1 is not available
Requirement 1 and 2 are not to hard to realize I would say
The idea of Requirment 3 and 4 is basically a easy to start (for my wife) fallback if something happens to the main server.
But I do not know how to do Requirement 3 and 4. At the beginning I thought I could do this with a cluster, but there I would need a third machine as quorum. If I run a cluster out of 2 nodes and one is powered off, nothing is working at all.
Wouln't it be enough that pve1 always runs the VMs, no matter how many nodes are available. pve2 only runs the VMs if only 1 node is available (pve1 can not be reached)
Any idea how this could be realized?