{"id":69385,"date":"2026-05-12T09:00:30","date_gmt":"2026-05-12T07:00:30","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=69385"},"modified":"2026-05-20T08:09:24","modified_gmt":"2026-05-20T06:09:24","slug":"veeam-high-availability-cluster-failover-and-automation-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-high-availability-cluster-failover-and-automation-pt-2\/","title":{"rendered":"Veeam High Availability Cluster: failover and automation - pt.2"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-69819 size-full\" title=\"veeam-high-availability-cluster-failover-and-automation-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-01.jpg\" alt=\"veeam-high-availability-cluster-failover-and-automation-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Once the Veeam High Availability Cluster has been created, there are two ways to perform the failover: manual and automated through <a href=\"https:\/\/www.veeam.com\/products\/veeam-data-platform\/monitoring-observability-ai.html\" target=\"_blank\" rel=\"noopener\">Veeam ONE<\/a>.<\/p>\n<p>Manual failover does not require additional components to be installed, whereas <strong>automatic failover requires Veeam ONE<\/strong> to be installed and configured within your network.<\/p>\n<p><!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Blog series<\/h2>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/how-to-configure-the-veeam-high-availability-cluster-pt-1\/\">How to configure the Veeam High Availability Cluster - pt.1<\/a><br \/>\nVeeam High Availability Cluster: failover and automation - pt.2<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-high-availability-cluster-switchover-and-disassemble-pt-3\/\">Veeam High Availability Cluster: switchover and disassemble - pt.3<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Primary node failure<\/h2>\n<p>To test whether the Veeam High Availability Cluster works as expected, you need to take the Primary Node offline by simulating a failure.<\/p>\n<p>From the vSphere Client, <strong>power off the Primary Node<\/strong> of the Veeam High Availability Cluster. Right click the Primary Node and select <strong>Power &gt; Power off<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-69820\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-02-600x296.jpg\" alt=\"\" width=\"600\" height=\"296\" title=\"\"><\/p>\n<p>Ensure the <strong>connection is lost<\/strong> from the <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-v13-upgrade-strategy-best-practices\/\">Veeam Backup &amp; Replication<\/a> Console.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-69821\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-03-600x333.jpg\" alt=\"\" width=\"600\" height=\"333\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h2>Manual failover of the Veeam High Availability Cluster<\/h2>\n<p>Once the Primary Node has failed, close and re-open the Veeam Console. The process takes <strong>about 10 minutes<\/strong> to complete the failover.<\/p>\n<p>Enter the <strong>IP Address of the HA Cluster<\/strong> and click <strong>Connect<\/strong>. You cannot initiate a failover using the cluster DNS name.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-69822\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-04.jpg\" alt=\"\" width=\"502\" height=\"424\" title=\"\"><\/p>\n<p>The <strong>new certificate thumbprint<\/strong> is detected. Click <strong>Yes<\/strong> to trust the server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-69823\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-05.jpg\" alt=\"\" width=\"502\" height=\"571\" title=\"\"><\/p>\n<p>The system detects the Primary Node has failed. Click <strong>Connect<\/strong> to connect to the Secondary Node.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-69824\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-06.jpg\" alt=\"\" width=\"502\" height=\"428\" title=\"\"><\/p>\n<p>Enter the credential to login to the Secondary Node and click <strong>Sign in<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-69825\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-07.jpg\" alt=\"\" width=\"502\" height=\"666\" title=\"\"><\/p>\n<p>Click <strong>Failover<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-69826\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-08.jpg\" alt=\"\" width=\"502\" height=\"477\" title=\"\"><\/p>\n<p>The system attempts to connect the cluster through the Secondary Node.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-69827\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-09.jpg\" alt=\"\" width=\"502\" height=\"461\" title=\"\"><\/p>\n<p>The Veeam Console now opens showing a warning about the <strong>missing Secondary Node<\/strong> in the HA Cluster. The previously configured Secondary Nodes has assumed the Primary Node role after failover.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-69828\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-10-600x281.jpg\" alt=\"\" width=\"600\" height=\"281\" title=\"\"><\/p>\n<p>This article has been written for\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/\" target=\"_blank\" rel=\"noopener noreferrer\">StarWind blog<\/a>\u00a0and can be found in\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/veeam-high-availability-cluster-failover-veeam-one\" target=\"_blank\" rel=\"noopener\">this page<\/a>. It covers the complete procedure for performing both<strong> manual and automated failovers of the Veeam High Availability Cluster<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Test automated failover<\/h2>\n<p>From the vSphere Client, <strong>Power Off<\/strong> the Veeam Primary Node (<em>veeam-v13sa<\/em> in the example).<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-69829\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-11-600x296.jpg\" alt=\"\" width=\"600\" height=\"296\" title=\"\"><\/p>\n<p>The Veeam Console <strong>loses the connection<\/strong> with the Primary Node.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-69830\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-12.jpg\" alt=\"\" width=\"340\" height=\"152\" title=\"\"><\/p>\n<p>In the Veeam ONE Client, go to the <strong>Veeam Backup &amp; Replication<\/strong> section and click on the grayed-out Primary Node. In the <strong>Alarms<\/strong> tab of the right pane, the <strong>failure of the node is detected<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-69831\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-13-600x248.jpg\" alt=\"\" width=\"600\" height=\"248\" title=\"\"><\/p>\n<p>The system requires <strong>about 10 minutes<\/strong> to complete the automated failover operation. When the failover is completed, the <strong>Secondary Node assumes the role of Primary Node<\/strong> restoring the Veeam Server functionality.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-69832\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2026\/04\/veeam-high-availability-cluster-failover-and-automation-14-600x249.jpg\" alt=\"\" width=\"600\" height=\"249\" title=\"\"><\/p>\n<p>Leveraging the Veeam ONE's capability to <strong>trigger an automated failover<\/strong> when the Primary Node fails allows you to maintain maximum efficiency of the <a href=\"https:\/\/nolabnoparty.com\/en\/using-the-veeam-deployment-kit\/\">Veeam Backup Server<\/a>, limiting the service outage to just a <strong>few minutes<\/strong>.<\/p>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/veeam-high-availability-cluster-switchover-and-disassemble-pt-3\/\">Part 3<\/a> will cover the procedure to s<strong>can, switchover and disassemble the HA Cluster<\/strong>.<\/p>\n<p>Read the\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/veeam-high-availability-cluster-failover-veeam-one\" target=\"_blank\" rel=\"noopener\">full article<\/a>\u00a0on StarWind blog.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Once the Veeam High Availability Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE. Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your network.<\/p>\n","protected":false},"author":3,"featured_media":69819,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"no","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[{"account":"linkedin_93tdZWzMZc_93tdZWzMZc","service":"linkedin","timestamp":1779256984,"status":"error"},{"account":"facebook_2879994398731222_17841400390232720","service":"facebook","timestamp":1778591760,"status":"queued"},{"account":"twitter_113568041_113568041","service":"twitter","timestamp":1779256987,"status":"error"},{"account":"mastodon_115463926174894442_115463926174894442","service":"mastodon","timestamp":1779256990,"status":"success"}],"rop_publish_now_status":"queued","footnotes":""},"categories":[2138,933],"tags":[579,2063,1957,3090],"class_list":["post-69385","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","tag-backup-en","tag-cluster-en","tag-failover-en","tag-veeam-one","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/69385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=69385"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/69385\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/69819"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=69385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=69385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=69385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}