Tuesday, May 12, 2026

Veeam High Availability Cluster: failover and automation – Part 2

After creating a Veeam High Availability Cluster, the next step is to verify how the environment behaves when the primary node becomes unavailable. In this part of the series, we walk through a simulated primary node failure and show how to perform a manual failover to the secondary node.

The article then explains how to use Veeam ONE to monitor the HA cluster state, detect primary node communication issues, and configure action handling for a faster recovery workflow. This helps reduce downtime for the Veeam Backup & Replication server and gives administrators better visibility into HA cluster events.

Primary node failure

To test whether the Veeam High Availability Cluster works as expected, you need to take the Primary Node offline by simulating a failure.

From the vSphere Client, power off the Primary Node of the Veeam High Availability Cluster. Right click the Primary Node and select Power > Power off.

 

wp-image-34101

 

Ensure the connection is lost from the Veeam Backup & Replication Console.

 

wp-image-34102

 

Manual failover of the Veeam High Availability Cluster

Once the Primary Node has failed, close and re-open the Veeam Console. The process takes about 10 minutes to complete the failover.

Enter the IP Address of the HA Cluster and click Connect. You cannot initiate a failover using the cluster DNS name.

 

wp-image-34104

 

The new certificate thumbprint is detected. Click Yes to trust the server.

 

wp-image-34105

 

The system detects the Primary Node has failed. Click Connect to connect to the Secondary Node.

 

wp-image-34106

 

Enter the credential to login to the Secondary Node and click Sign in.

 

wp-image-34107

 

Click Failover.

 

wp-image-34108

 

The system attempts to connect the cluster through the Secondary Node.

 

wp-image-34109

 

The Veeam Console now opens showing a warning about the missing Secondary Node in the HA Cluster. The previously configured Secondary Nodes has assumed the Primary Node role after failover.

 

wp-image-34111

 

Automate failover operation with Veeam ONE

Although manual failover is a simple task to perform, an automated failover process can be a better and more efficient option to maintain protection for mission-critical VMs.

 

wp-image-34112

 

To automate the failover operation for a Veeam High Availability Cluster, Veeam ONE must be installed in your infrastructure. Make sure Veeam ONE is installed and configured.

Enable monitoring in the Veeam appliance

To configure automated failover, you need to register the two Veeam 13 Appliances in Veeam ONE. To allow correct registration with Veeam ONE, you need to enable Data Collection from the Veeam Host Management Console.

Using your preferred browser, type the address https://<Veeam_Primary_Node>:10443. Enter the veeamadmin credentials and click Sign in.

 

wp-image-34113

 

Go to Backup Infrastructure and click Submit Request in the Data Collection section.

 

wp-image-34114

 

Click OK.

 

wp-image-34115

 

The request is placed in Waiting for approval status. Click veeamadmin > Sign out to logoff the current user.

 

wp-image-34116

 

Enter the veeamso (security officer) credentials and click Sign in.

 

wp-image-34117

 

Select the pending request and click Approve.

 

wp-image-34118

 

Once the request has been approved, click veeamso > Sign out.

 

wp-image-34119

 

Login again with the veeamadmin account to verify the request is displayed as Request Approved.

 

wp-image-34120

 

Before proceeding with the configuration of Veeam ONE, repeat the same procedure for the Secondary Node.

Register Veeam Nodes in Veeam ONE

Access the Veeam ONE server and login to the Veeam ONE Web Client.

 

wp-image-34121

 

In the Overview tab, click Data Source > Add server.

 

wp-image-34122

 

Select Veeam Backup & Replication.

 

wp-image-34123

 

Enter the DNS name or IP Address of the Primary Node then click Next.

 

wp-image-34124

 

Click Add credentials to specify the user for authenticating against the Primary Node.

 

wp-image-34125

 

Select Standard account.

 

wp-image-34126

 

Specify the veeamadmin credentials and click Finish.

 

wp-image-34127

 

Make sure veeamadmin is seleted in the Credentials drop-down menu and click Next.

 

wp-image-34128

 

Click Trust and Continue to accept the certificate.

 

wp-image-34129

 

Click Finish to register the Primary Node.

 

wp-image-34130

 

The system detects the node members of the cluster and starts installing the required agents.

 

wp-image-34131

 

After a few seconds, the agents are installed successfully.

 

wp-image-34132

 

Configure automated failover

Now login to Veeam ONE Client and click Connect to proceed with the configuration of the automated Veeam High Availability Cluster failover.

 

wp-image-34133

 

Go to the Alert Management area and select Veeam Backup & Replication. In the Filter box type ha cluster to filter HA cluster options.

 

wp-image-34134

 

Right click Veeam Backup & Replication HA cluster primary node state and select Edit.

 

wp-image-34135

 

Navigate to the Action section and select Automatic in the Execution type drop-down menu. Clic Save to save the configuration.

 

wp-image-34136

 

Test automated failover

From the vSphere Client, Power Off the Veeam Primary Node (veeam-v13sa in the example).

 

wp-image-34137

 

The Veeam Console loses the connection with the Primary Node.

 

wp-image-34138

 

In the Veeam ONE Client, go to the Veeam Backup & Replication section and click on the grayed-out Primary Node. In the Alarms tab of the right pane, the failure of the node is detected.

 

wp-image-34139

 

The system requires about 10 minutes to complete the automated failover operation. When the failover is completed, the Secondary Node assumes the role of Primary Node restoring the Veeam Server functionality.

 

wp-image-34140

 

Leveraging the Veeam ONE’s capability to trigger an automated failover when the Primary Node fails allows you to maintain maximum efficiency of the Veeam Backup Server, limiting the service outage to just a few minutes.



from StarWind Blog https://ift.tt/2NQGqeS
via IFTTT

No comments:

Post a Comment