Proxmox Replication Configuration Beginners Guide

Learn about Proxmox replication and how it helps with data integrity and makes sure of high availability. Learn to config step-by-step.

 

Proxmox offers excellent built-in disaster recovery tools that require no additional add-ons or licensing. One notable feature is its replication capability, which enables the replication of VMs stored on local ZFS storage to a target node, even without shared storage. Let’s explore Proxmox replication in detail and learn how to configure it.

What is Proxmox Replication?

Proxmox replication facilitates the duplication of VM data across multiple nodes within a cluster. This process is integral to maintaining data integrity and ensuring that services remain available even in the event of a node failure.

Why is replication helpful?

Replication has long been a helpful element of a successful disaster recovery strategy since it duplicates your virtual disks from a source host to a target. In the event the source virtual host goes down for whatever reason, the replication task has created the virtual machine or container on the second node and you can start up the virtual resource on the second node.

Advantages of Proxmox replication

It also provides the following advantages for system administrators building their virtualization solution on top of Proxmox:

• Data Security: It bolsters data protection by creating additional copies of critical VM data across multiple nodes.
• High Availability: It helps to make sure in the event of a hardware failure, other nodes can immediately take over critical workloads for system uptime
• Scalability: Facilitates easy scaling of services and data across additional nodes without significant downtime.

Prerequisites for Proxmox Replication task

Proxmox replication is configured based on several key prerequisites:

ZFS Storage

ZFS storage is known for the built-in data protection capabilities that you can take advantage of, nicluding block-level data replication, which is more frequent and accurate than file-level replication, ensuring that all replicated data remains consistent and up-to-date across different storage media.

Two Proxmox VE Servers

Replication of Proxmox VMs cannot be performed on the same node; it requires at least two Proxmox nodes to set up a replication task. During replication, the VM’s underlying storage is transferred from the source node to a different node.

Furthermore, the same storage cannot be used for replication. A separate storage location must be designated as the target for the replication task.

Access to the command line or Proxmox web interface

To set up a replication task in Proxmox, administrators can use the command line tool to specify the source VM, target node, and replication schedule. They can also use the web interface as we will demonstrate below.

Configuring Proxmox Replication

Note the following overview of steps to create a Proxmox replication task:

Step-by-Step Configuration

1. Select Virtual Machines: Choose which VMs need replication. You choose the VM based on the ID of the virtual machine.
2. Determine the Target Node: Assign a secondary node where the VM data will be replicated. This node will be the backup in case the primary node fails.
3. Define Replication Schedules: Using the following command, schedule how often the VM data should replicate to ensure minimal data loss: replicate --vmid --target-node --schedule.
4. Monitor and Adjust: Continuously monitor the replication process to ensure optimal performance. Adjust the replication parameters as needed based on system load and network capacity.

To begin adding the replication task in Proxmox, navigate to Datacenter > Replication > Add.

Select the virtual machine or LXC container ID you want to replicate:

Under the schedule drop down list, you will see the various options you can choose for scheduling the replication task to start automatically.

As you can see below, you can also set a rate limit on the replication task in addition to the other configuration options to minimize impact on the public network.

A replication job is identified by a cluster-wide unique ID. This ID is composed of the VMID in addition to a job number. This ID must only be specified manually if the CLI tool is used.

Troubleshooting the Proxmox Replication task

While Proxmox replication is powerful, you may run into the need to troubleshoot when it doesn’t work as expected

• Managing Network Load: Network resources are being saturated because Proxmox replication tasks consume significant bandwidth. To reduce the impact of network saturation caused by Proxmox replication, you can set rate limits and schedule replication tasks during periods of low network traffic.
• At least two nodes required: If you get an error about at least two nodes being needed for Proxmox replication, you most likely don’t have more than one node added to your Proxmox data center.
• Optimizing Storage Usage: Continuous replication can lead to using up available storage. Regular audits and alerting are necessary to manage storage capacity effectively.
• VM storage is not enabled for replication: You may get an error similar to the “VM storage is not enabled” for replication. This type of error generally points to an issue with ZFS not being provisioned or the VM storage resides on local LVM storage, instead of ZFS.

Next steps

The next steps when you want to get a feel for Proxmox replication is to first make sure you have the prerequisites met:

• Make sure you have ZFS storage provisioned and you have at least two Proxmox nodes
• Make sure you have good network connectivity between your source Proxmox host and the target Proxmox host for replication.
• Verify you have the VM ID or LXC container ID ready for creating the Proxmox replication task.
• Name the replication task intuitively in the description
• Test your replication task. Make sure to test your Proxmox replication task before you need to rely on it for disaster recovery.

Wrapping up Proxmox replication

Replication is an excellent way to enhance your disaster recovery strategy. It supports the 3-2-1 backup best practice by creating multiple copies of your data, ensuring at least one copy is stored offsite when replicating to a different data center.

Proxmox makes this process even more accessible by including replication tools directly within Proxmox VE Server, without requiring a subscription license. However, it’s important to meet the prerequisites: your virtual machines must be stored on ZFS storage, and you need more than one Proxmox VE Server added to your Proxmox data center.