Proxmox Failover: Replica VM 2 Nodes
This article describes the process of creating a failover system for Proxmox virtual machines (VMs) using 2-node replication, with ZFS Raid for data redundancy, an external GCP bucket for relocating backups to Cloud Storage, and Icinga2 monitoring.
Index
Introduction
Proxmox Virtual Environment (VE) is an open-source virtualization platform widely used for virtual machine (VM) management. Its failover feature ensures business continuity in the event of hardware or software failure, by replicating VMs to a backup node, they can be activated when needed.
In this paper, we will present our VM replication project on 2 Proxmox nodes, with the goal of creating an available and resilient failover system. We will describe the system architecture, the VM replication process, the failover mechanism, and the benefits obtained.
Project description
Our failover system is based on a 2-node Proxmox architecture, with one VM replicated on each node. For data storage, we used ZFS raid (RAIDZ) to ensure redundancy and protection against disk failures. In addition, we integrated an external GCP bucket for relocating backups, providing an additional layer of security and data protection.
The VM replication process is done through the Proxmox VE web interface via scheduling. VMs are replicated incrementally, synchronizing storage changes via the network, using ZFS capabilities.
The failover mechanism is based on monitoring the status of the primary node. In the event of a failure, monitoring alerts the failure and the replicated VM can be activated. This ensures fast recovery and minimizes service interruptions.
Advantages and Benefits
Our VM failover system offers numerous advantages, including:
- Downtime Reduction: Failover minimizes VM downtime.
- Data Protection: ZFS Raids and de-localized backup on GCP buckets ensure data security and integrity.
Technical details
Our project used the following configurations:
- Proxmox VE: Version 6.0, currently upgraded to version 8
- Network: Dedicated VLANs for communication between nodes and VMs
During the project, we encountered some technical challenges, including configuring VLAN routing and optimizing backup performance. We overcame them with extensive research and rigorous testing.
FAQ
D: What are the hardware requirements to implement this failover system?
R: The hardware requirements depend on the number of VMs and the expected workload. In general, it is recommended to use server grade HW and expect the load to increase in the short to medium term both as disk and RAM usage.
D: How can I monitor the status of my failover system?
R: You can use the web interface of Proxmox VE or integrate an external monitoring system such as Icinga2.
D: Can I use this failover system with other virtualization platforms?
R: The basic principles of failover are similar among different virtualization platforms. However, the specific configuration may vary.
Free Consultation
Are you looking for a reliable and secure solution for your Proxmox VE virtualization? Check out our proxmox consulting and support, free, no-obligation call to evaluate the best configuration
Concluding remarks
In this article, we have presented our VM replication project on 2 Proxmox nodes, highlighting its advantages and technical implementation. This solution is effective in ensuring the availability and resilience of VMs in virtualized environments.
High-reliability solutions with automatic VM migration are deployable using 3 nodes and shared storage
