{"id":22766,"date":"2018-01-22T09:00:58","date_gmt":"2018-01-22T08:00:58","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=22766"},"modified":"2023-07-16T11:27:57","modified_gmt":"2023-07-16T09:27:57","slug":"vmware-vcenter-high-availability-maintenance-test-failover-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-vcenter-high-availability-maintenance-test-failover-pt-2\/","title":{"rendered":"VMware vCenter High Availability: maintenance and test failover - pt.2"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-23092 size-full\" title=\"vcha-maintenance-test-failover-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-01.jpg\" alt=\"vcha-maintenance-test-failover-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Once the HA cluster has been created, the vCenter High Availability maintenance and test failover procedures ensure the <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-5-deployment-pt1\/\">VCSA 6.5<\/a> is protected against multiple types of <strong>hardware and software failures<\/strong>.<\/p>\n<p>When the vCenter Server nodes (Active, Passive and Witness) have been deployed, the\u00a0<strong>maintenance and test failover<\/strong>\u00a0of the HA cluster should be performed on regular basis to guarantee a\u00a0<strong>working and protected<\/strong>\u00a0cluster.<\/p>\n<p><!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Blog Series<\/h2>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcenter-high-availability-setup-pt-1\/\">VMware vCenter High Availability: setup - pt.1<\/a><br \/>\nVMware vCenter High Availability: maintenance and test failover - pt.2<\/p>\n<p>&nbsp;<\/p>\n<h2>Monitoring the HA cluster status<\/h2>\n<p>Checking the vCenter Server HA status on regulare basis, ensures the maximum protection for the <strong>virtual infrastructure functionality<\/strong>.<\/p>\n<p>To check the current status of the HA cluster, open the vSphere Web Client and select\u00a0<strong>Configure &gt; vCenter HA<\/strong>. Click <strong>vCenter HA Monitoring<\/strong>\u00a0to access the monitoring window.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23093 size-large\" title=\"vcha-maintenance-test-failover-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-02-600x361.jpg\" alt=\"vcha-maintenance-test-failover-02\" width=\"600\" height=\"361\" \/><\/p>\n<p>The window displays the current status of the Active, Passive and Witness nodes. Click <strong>vCenter HA Settings<\/strong> to go back to the management page.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23094 size-large\" title=\"vcha-maintenance-test-failover-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-03-600x361.jpg\" alt=\"vcha-maintenance-test-failover-03\" width=\"600\" height=\"361\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>HA cluster maintenance<\/h2>\n<p>The HA cluster is enabled by default and performs an <strong>automated failover<\/strong> when a failure occurs. If you need to control the behavior of the HA cluster, from the <strong>vCenter HA<\/strong> area click on\u00a0<strong>Edit<\/strong> button.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23095 size-large\" title=\"vcha-maintenance-test-failover-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-04-600x361.jpg\" alt=\"vcha-maintenance-test-failover-04\" width=\"600\" height=\"361\" \/><\/p>\n<p>Selecting the\u00a0<strong>Maintenance mode<\/strong> option, the automatic failover is disabled but <strong>replication still works<\/strong> between Active and Passive nodes. Click <strong>OK<\/strong> to\u00a0 confirm. This option is used during the update procedure of the vCenter Server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23096 size-full\" title=\"vcha-maintenance-test-failover-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-05.jpg\" alt=\"vcha-maintenance-test-failover-05\" width=\"507\" height=\"372\" \/><\/p>\n<p>When the HA cluster is in Maintenance Mode, the current <strong>Status<\/strong> is displayed in the table.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23097 size-large\" title=\"vcha-maintenance-test-failover-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-06-600x399.jpg\" alt=\"vcha-maintenance-test-failover-06\" width=\"600\" height=\"399\" \/><\/p>\n<p>Selecting <strong>Disable vCenter HA<\/strong>\u00a0option, it disables <strong>both\u00a0failover and replication<\/strong> but HA configuration <strong>remains intact<\/strong>. Click <strong>OK<\/strong> to confirm.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23098 size-full\" title=\"vcha-maintenance-test-failover-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-07.jpg\" alt=\"vcha-maintenance-test-failover-07\" width=\"507\" height=\"372\" \/><\/p>\n<p>When the HA cluster is disabled, the current <strong>Status<\/strong> is displayed in the table.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23099 size-large\" title=\"vcha-maintenance-test-failover-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-08-600x400.jpg\" alt=\"vcha-maintenance-test-failover-08\" width=\"600\" height=\"400\" \/><\/p>\n<p>Selecting the <strong>Remove vCenter HA<\/strong> option the HA cluster is <strong>completely removed<\/strong>\u00a0but the Active node continues to run normally.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23101 size-full\" title=\"vcha-maintenance-test-failover-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-09.jpg\" alt=\"vcha-maintenance-test-failover-09\" width=\"507\" height=\"372\" \/><\/p>\n<p>If the HA cluster is in Maintenance Mode or Disabled, select <strong>Enable vCenter HA<\/strong> to restore the default HA cluster functionality.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23103 size-full\" title=\"vcha-maintenance-test-failover-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-10.jpg\" alt=\"vcha-maintenance-test-failover-10\" width=\"507\" height=\"372\" \/><\/p>\n<p>When the HA cluster is enabled, it requires <strong>some minutes before the automatic failover protection is available<\/strong> again since the intial replication may still be\u00a0in progress.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23104 size-large\" title=\"vcha-maintenance-test-failover-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-11-600x187.jpg\" alt=\"vcha-maintenance-test-failover-11\" width=\"600\" height=\"187\" \/><\/p>\n<p>The vCenter HA is available again and the automatic failover protection is enabled.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23105 size-large\" title=\"vcha-maintenance-test-failover-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-12-600x400.jpg\" alt=\"vcha-maintenance-test-failover-12\" width=\"600\" height=\"400\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Backup and Restore<\/h2>\n<p>As backup strategy, backup the <strong>Active node only<\/strong> skipping the Passive and Witness nodes. In case you need to <strong>restore the Active node<\/strong>, you must <strong>remove the HA cluster<\/strong> configuration, restore and <strong>re-create the HA cluster<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23106 size-full\" title=\"vcha-maintenance-test-failover-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-13.jpg\" alt=\"vcha-maintenance-test-failover-13\" width=\"507\" height=\"372\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Testing failover<\/h2>\n<p>To test the failover, from <strong>Configure &gt; vCenter HA<\/strong> area click the <strong>Initiate Failover<\/strong> button.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23107 size-large\" title=\"vcha-maintenance-test-failover-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-14-600x331.jpg\" alt=\"vcha-maintenance-test-failover-14\" width=\"600\" height=\"331\" \/><\/p>\n<p>Flag the <strong>Force the failover...<\/strong> option then click <strong>Yes<\/strong> to initiate the failover.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23109 size-full\" title=\"vcha-maintenance-test-failover-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-15.jpg\" alt=\"vcha-maintenance-test-failover-15\" width=\"398\" height=\"222\" \/><\/p>\n<p>You can view the <strong>failover progress<\/strong> from the browser by using, of course, same DNS name or IP address. VMware reports an <strong>RTO of 5 minutes<\/strong>, maybe a little bit to high but surely will be improved in future releases.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23110 size-large\" title=\"vcha-maintenance-test-failover-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-16-600x291.jpg\" alt=\"vcha-maintenance-test-failover-16\" width=\"600\" height=\"291\" \/><\/p>\n<p>The <strong>Passive node took over<\/strong> the Active role and the HA IP address (in the example 192.168.70.10) remained, as expected, the same.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23112 size-large\" title=\"vcha-maintenance-test-failover-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-17-600x340.jpg\" alt=\"vcha-maintenance-test-failover-17\" width=\"600\" height=\"340\" \/><\/p>\n<p>When the Active node comes back, the normal status is restored.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23118 size-large\" title=\"vcha-maintenance-test-failover-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-maintenance-test-failover-18-600x359.jpg\" alt=\"vcha-maintenance-test-failover-18\" width=\"600\" height=\"359\" \/><\/p>\n<p>Configuring the vCenter Server HA ensure an <strong>higher level of protection<\/strong> for your virtual environment with <strong>no extra licenses<\/strong> required. Testing failover is the good way to make sure that everything <strong>works as expected<\/strong>.<\/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 HA cluster has been created, the vCenter High Availability maintenance and test failover procedures ensure the VCSA 6.5 is protected against multiple types of hardware and software failures. When the vCenter Server nodes (Active, Passive and Witness) have been deployed, the\u00a0maintenance and test failover\u00a0of the HA cluster should be performed on regular basis to guarantee a\u00a0working and protected\u00a0cluster.<\/p>\n","protected":false},"author":3,"featured_media":23092,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[1781,1805,467,583],"class_list":["post-22766","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-failover","tag-high-availability","tag-maintenance","tag-vcenter-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/22766","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=22766"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/22766\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/23092"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=22766"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=22766"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=22766"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}