{"id":28730,"date":"2023-06-15T17:26:13","date_gmt":"2023-06-15T15:26:13","guid":{"rendered":"https:\/\/blog.miniserver.it\/?p=28730"},"modified":"2023-06-15T17:26:15","modified_gmt":"2023-06-15T15:26:15","slug":"2-node-proxmox-ve-cluster-how-it-works","status":"publish","type":"post","link":"https:\/\/blog.miniserver.it\/en\/proxmox-ve\/2-node-proxmox-ve-cluster-how-it-works\/","title":{"rendered":"2 Node Proxmox VE Cluster: How it Works"},"content":{"rendered":"

A 2 Node Cluster Proxmox VE consists of two servers connected to each other, able to work together to provide processing and storage resources.<\/span><\/p>\n

In this article, we will illustrate what the 2 node Proxmox VE Cluster is made up of, and the advantages it can offer, such as continuous synchronization (or replication) between the two nodes, live migration of VMs and backup management with Proxmox Backup Server.<\/p>\n<\/div><\/div><\/div>

How does the 2 node Proxmox VE cluster work?<\/h2><\/div>
<\/div><\/div><\/div><\/div>

1. Node 1 and node 2<\/h2>\n

To create a cluster-level interaction between these two nodes, it is necessary to set the data synchronization frequency which we will call Delta T here.<\/p>\n

Delta T refers to the time difference between two events, in this case the synchronization (or as Proxmox calls it “replication”) of data between the two Nodes.<\/p>\n

In data replication between two Nodes, Delta T is used to indicate the time elapsed between the last data replication and the next. In other words, Delta T indicates the amount of time elapsed between copying data from one node to another.<\/p>\n

Delta T values can be modified at will, but the hardware characteristics of the Hosts must be kept in mind. The more performing the Hosts are from a hardware point of view, the more it will be possible to set a low Delta T value and thus obtain very frequent replicas.<\/p>\n

Delta T is influenced by factors such as the speed of the network connection between the two Hosts, the amount of data to be synchronized, the distance between the Hosts and other factors. Therefore, Delta T can vary based on these factors and should not be changed lightly.<\/p>\n<\/div>

\"Sincronizazzione<\/span><\/div>

2. Resource migration between the two nodes<\/h2>\n

With continuous cluster-level replication between Node One and Node Two, running resources can be easily migrated from one node to another.<\/p>\n

Live migration of running VMs between nodes, or “migration in place”, allows you to move a virtual server from one physical host to another physical host without disrupting running services or applications on the server.<\/p>\n

During running migration, the virtual server is moved from the first host to the second host through a high-speed network connection, with the support of Proxmox VE (Virtual Environment).<\/p>\n

During the migration process, virtual servers continue to function normally with no disruption to end users.<\/p>\n

Running resource migration minimizes downtime and improves system scalability, making it easier to manage computing resources and data.<\/p>\n<\/div>

\"Migrazione<\/span><\/div>
<\/div><\/div>
<\/div><\/div>

3. Backup tasks<\/h2>\n

The third hardware device inside the 2 node cluster is a Proxmox Backup Server, which has two very important roles:<\/p>\n

    \n
  • Contain all versions of file backups.<\/li>\n
  • Create a third node for cluster setup and operation.<\/li>\n<\/ul>\n

    Proxmox Backup Server is not a computing node, but it is the host that stores the backups.<\/p>\n

    The Proxmox Backup Server is not a computing node, but it is the host that maintains the backups.<\/p>\n

    From the 2 node cluster, you can create backup Tasks with Proxmox Backup Server.<\/p>\n

    Scheduled backup tasks back up virtual machines, containers and other data incrementally, automatically and periodically.<\/p>\n

    Furthermore, backup tasks on Proxmox Backup Server minimize the risk of data loss and improve data reliability and security within a virtualization environment.<\/p>\n<\/div>

    \"Task<\/span><\/div>

    4. Backup versioning<\/h2>\n

    As a result, you get different backup versions of services, based on the frequency of backup task scheduling.<\/p>\n

    Backup versioning on Proxmox Backup Server is a function that allows you to maintain multiple backup copies of a single virtual server or physical machine.<\/p>\n

    This means that you can create a series of incremental backups over time, so that you can access previous versions of your data and files in the event of a problem or data loss.<\/p>\n

    Backup versioning creates a new incremental backup copies each time the virtual server or physical machine is backed up.<\/p>\n

    This way, you can access multiple versions of the backup.<\/p>\n<\/div>

    \"Versioning<\/span><\/div>

    5. Backup service restore<\/h2>\n

    By choosing a specific version, you can perform restores, on the cluster, of a particular version of VM, container or resource.<\/p>\n

    It is also possible to easily recover and download single files inside VMs or containers, through the browsing implemented by Proxmox Backup Server. VMs can have any type of operating system.<\/p>\n<\/div>

    \"Restore<\/span><\/div>

    This is the overview of the basic configuration of the Proxmox VE Two Node Cluster.<\/p>\n

    A 2 node Proxmox VE cluster can also be extended or transformed into a multi-node cluster by adding additional nodes to it, thus guaranteeing flexibility and scalability.<\/p>\n

    From a budget point of view, a 2 node Proxmox VE cluster allows you to start from a basic solution, that can be extended in the future, always maintaining the services.<\/p>\n<\/div><\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":11,"featured_media":27887,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[129],"tags":[],"class_list":["post-28730","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-proxmox-ve"],"_links":{"self":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/28730","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/comments?post=28730"}],"version-history":[{"count":21,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/28730\/revisions"}],"predecessor-version":[{"id":28763,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/28730\/revisions\/28763"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media\/27887"}],"wp:attachment":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media?parent=28730"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/categories?post=28730"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/tags?post=28730"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}