Veeam Backup & Replication v13 adds High Availability for the backup server. Our latest guide covers the setup path, so you don’t hit dead ends mid-deploy.
Veeam Backup & Replication v13 introduces the High Availability Cluster for Linux-based backup servers, helping keep the backup infrastructure available if the primary Backup Server becomes unavailable. The feature uses two Veeam Software Appliances, a cluster DNS name, a virtual IP address, and configuration database synchronization between the primary and secondary nodes.
In this first part of the series, we’ll walk through the initial HA cluster configuration: checking the prerequisites, enabling High Availability on both appliances, creating the cluster in the Veeam Backup & Replication Console, and connecting to the new cluster endpoint.
Before starting the configuration, make sure both nodes meet the required conditions: the same Veeam version, proper forward and reverse DNS records, static IP addresses in the same subnet, and a Veeam Data Platform Premium license. Local repositories should not be used within the HA cluster.
Prerequisites
To configure a working Veeam High Availability Cluster, you need the following:
- Linux-based Veeam Backup Server – the configuration of the HA cluster works only with the Linux appliance version of the Veeam Backup Server. A mixed cluster with Windows and Linux Backup Servers is not supported. If a Veeam appliance is already configured and in use in the backup infrastructure, you can deploy a new appliance to use as a secondary node. Keep in mind that local repositories cannot be used within the HA cluster.
- Veeam version – both nodes must have the same Veeam version installed before creating the HA cluster.
- Veeam Backup console – to manage the HA cluster, the Veeam console installed on a Windows machine is required.
- DNS Server – the cluster, primary node and secondary node must be defined in the DNS records in both forward and reverse zones.
- Layer 2 network – both nodes must reside in the same subnet (layer 2) to establish proper communication.
- License – the Veeam Data Platform Premium License is required to create the HA cluster.
How Veeam High Availability cluster works
Once the HA cluster has been created, Veeam leverages a PostgreSQL function to establish which is the primary and which is the secondary node of the cluster. Then, the synchronization between the HA nodes takes place. Changes in the Veeam configuration are always written to the primary node first and then replicated to the secondary node.
If the secondary node goes offline for more than 10 minutes, a warning is displayed on the notification bar of the primary node and an email alert is sent to the address specified in the global email notification settings. Another email will be sent once the secondary nodes comes back online.
Upgrading the HA cluster
Veeam leverages the Veeam Updater service to upgrade the HA cluster. During the upgrade operation, the primary node is upgraded first then the updates are synchronized with the secondary node. Automatic updates on the secondary node are disabled.
Updates available in the secondary node are compared with the updates installed on the primary node, and then only the necessary updates are installed on the secondary node.
Configure the Veeam High Availability cluster
Deploy two Veeam Software Appliances that will serve as primary and secondary node of the High Availability Cluster. The secondary node must be a new installation and cannot contain any existing backup data.
Enable High Availability
To create the HA cluster, you must submit a request to enable the High Availability on both servers. Using your preferred browser, access the Veeam Host Management at https://<IP_Address>:10443. Enter the correct credentials (veeamadmin in the example) and click Sign in.
Enter the MFA code, then click Sign in.
Go to Backup Infrastructure area and click the Submit Request in the High Availability section.
Click OK.
The request will now show a Waiting for approval status, pending approval by the Security Officer.
Login to the Veeam Host Management using the Security Officer credentials and click Sign in.
Enter the MFA code, then click Sign in.
Select the pending request and click Approve.
Once approved, exit Veeam Host Management.
If you login again using Backup Administrator credentials, the request will now be displayed as Request approved.
Repeat the same procedure for the secondary node.
Create the HA cluster
Using the Veeam Backup & Replication Console, access the primary node. In the Backup infrastructure area, go to Managed Servers > Linux. Right click the Veeam Backup Server and select Create HA cluster.
If the Create HA cluster option is not available, it means the Veeam Data Platform Premium License is not installed on the Backup Server.
Verify that the installed license is the Premium edition.
Enter the Cluster DNS name created in the DNS Server and the Virtual IP address. Click Next.
Select the Primary node IP address and type the Secondary node IP address. Specify the correct Credentials to use and click Next.
Click Continue.
Click Finish to start the initialization.
The Veeam High Availability Cluster is being created.
After the HA cluster has been created, you can easily identify the primary and secondary node.
Connect to the High Availability Cluster
Once the HA cluster has been created, you must access the infrastructure management by entering the DNS HA cluster name in the Veeam Console. Click Connect.
Click Yes to accept the certificate.
Enter the credentials and click Sign in.
The Veeam Backup & Replication v13 main dashboard.
With the Veeam Backup Server in HA mode, you have the opportunity to quickly recover the backup infrastructure functionality if anything goes wrong with the primary node.
Part 2 will cover the manual failover procedure and the configuration required to trigger the failover operation automatically using Veeam ONE.
from StarWind Blog https://ift.tt/8a7SxRU
via IFTTT
No comments:
Post a Comment