{"id":23820,"date":"2018-03-20T09:00:50","date_gmt":"2018-03-20T08:00:50","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=23820"},"modified":"2018-03-21T12:25:38","modified_gmt":"2018-03-21T11:25:38","slug":"shutdown-vsan-cluster-vcenter-running-datastore","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/shutdown-vsan-cluster-vcenter-running-datastore\/","title":{"rendered":"Shutdown the vSAN cluster with vCenter running on the datastore"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-23821 size-full\" title=\"vsan-cluster-shutdown-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-01.jpg\" alt=\"vsan-cluster-shutdown-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>To shutdown the <a href=\"https:\/\/nolabnoparty.com\/en\/virtual-san-2-node-cluster-installtion-robo-pt1\/\">vSAN cluster<\/a> with vCenter running on the datastore, you need to follow a specific procedure to <strong>avoid data loss<\/strong>\u00a0keeping the <strong>cluster configuration healthy<\/strong>.<\/p>\n<p>In addition, if the vCenter Server Appliance (vCSA) is stored in the vSAN cluster, you need to follow a specific sequence to properly shutdown the running VMs.<!--more--><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23822 size-full\" title=\"vsan-cluster-shutdown-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-02.jpg\" alt=\"vsan-cluster-shutdown-02\" width=\"511\" height=\"437\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Shutdown VMs<\/h2>\n<p>There are several reasons why you would shutdown the entire vSAN cluster and if the vSAN is the main storage used in your virtual infrastructure, most probabily also the <strong>vCenter Server resides in the vSAN cluster<\/strong>. With this scenario you need to shutdown the VMs properly.<\/p>\n<p>From the vSphere Web Client, select the vSAN cluster and go to <strong>VMs<\/strong> tab. Shutdown all running virtual machines <strong>except the vCSA<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23823 size-large\" title=\"vsan-cluster-shutdown-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-03-600x437.jpg\" alt=\"vsan-cluster-shutdown-03\" width=\"600\" height=\"437\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to confirm the shutdown of selected VMs.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23824 size-full\" title=\"vsan-cluster-shutdown-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-04.jpg\" alt=\"vsan-cluster-shutdown-04\" width=\"414\" height=\"112\" \/><\/p>\n<p>The VMs have been shutdown.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23825 size-large\" title=\"vsan-cluster-shutdown-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-05-600x434.jpg\" alt=\"vsan-cluster-shutdown-05\" width=\"600\" height=\"434\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Move the vCenter Server to the first ESXi host<\/h4>\n<p>Write down on which host the vCenter resides or, as recommended by VMware, migrate the vCenter to the <strong>first ESXi host<\/strong> to easily find the VM when the vSAN cluster is powered on again.<\/p>\n<p>Right click the vCenter Server and select <strong>Migrate<\/strong> to move the VM to the first ESXi if currently resides on a different host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23826 size-large\" title=\"vsan-cluster-shutdown-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-06-600x294.jpg\" alt=\"vsan-cluster-shutdown-06\" width=\"600\" height=\"294\" \/><\/p>\n<p>Select <strong>Change compute resource only<\/strong> option and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23827 size-large\" title=\"vsan-cluster-shutdown-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-07-600x351.jpg\" alt=\"vsan-cluster-shutdown-07\" width=\"600\" height=\"351\" \/><\/p>\n<p>Select the first host and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23828 size-large\" title=\"vsan-cluster-shutdown-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-08-600x351.jpg\" alt=\"vsan-cluster-shutdown-08\" width=\"600\" height=\"351\" \/><\/p>\n<p>Select the correct network and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23833 size-large\" title=\"vsan-cluster-shutdown-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-09-600x351.jpg\" alt=\"vsan-cluster-shutdown-09\" width=\"600\" height=\"351\" \/><\/p>\n<p>Select <strong>Schedule vMotion with high priorty<\/strong> option and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23834 size-large\" title=\"vsan-cluster-shutdown-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-10-600x351.jpg\" alt=\"vsan-cluster-shutdown-10\" width=\"600\" height=\"351\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to migrate the VM.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23835 size-large\" title=\"vsan-cluster-shutdown-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-11-600x351.jpg\" alt=\"vsan-cluster-shutdown-11\" width=\"600\" height=\"351\" \/><\/p>\n<p>Make sure the vCSA has been <strong>migrated to the first ESXi<\/strong> host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23836 size-large\" title=\"vsan-cluster-shutdown-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-12-600x241.jpg\" alt=\"vsan-cluster-shutdown-12\" width=\"600\" height=\"241\" \/><\/p>\n<p>If your environment uses <strong>Active Directory<\/strong>, I recommend to migrate to the first ESXi host also a <strong>Domain Controller<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Shutdown the vSAN cluster<\/h2>\n<p>From the <strong>Inventory<\/strong> view, select the <strong>vSAN cluster<\/strong> then go to <strong>Monitor &gt; vSAN<\/strong>. Select <strong>Resyncing Components<\/strong> tab and verify no vSAN components are currently resyncing before putting the hosts members of the vSAN cluster in Maintenance Mode.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23837 size-large\" title=\"vsan-cluster-shutdown-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-13-600x295.jpg\" alt=\"vsan-cluster-shutdown-13\" width=\"600\" height=\"295\" \/><\/p>\n<p>If no resyncing is occuring in the cluster, right click the vCenter Server and select <strong>Power &gt; Shut Down Guest OS<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24105 size-large\" title=\"vsan-cluster-shutdown-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-14-600x373.jpg\" alt=\"vsan-cluster-shutdown-14\" width=\"600\" height=\"373\" \/><\/p>\n<p>This action makes the vSphere Web Client unavailable.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24106 size-full\" title=\"vsan-cluster-shutdown-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-15.jpg\" alt=\"vsan-cluster-shutdown-15\" width=\"380\" height=\"112\" \/><\/p>\n<p>To shutdown hosts member of the vSAN cluster, you can proceed <strong>via GUI<\/strong> or using the ESXCLI command.\u00a0From the vSphere Host Client, right click <strong>Host<\/strong> and select <strong>Enter maintenance mode<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24107 size-full\" title=\"vsan-cluster-shutdown-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-16.jpg\" alt=\"vsan-cluster-shutdown-16\" width=\"480\" height=\"458\" \/><\/p>\n<p>Make sure <strong>vSAN data migration<\/strong> is set as <strong>No data migration<\/strong>\u00a0option because we are going to put all hosts into Maintenance Mode to shutdown the cluster then there is <strong>no reason to migrate VMs<\/strong> between hosts. Click <strong>Yes<\/strong> to proceed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24108 size-large\" title=\"vsan-cluster-shutdown-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-17-600x384.jpg\" alt=\"vsan-cluster-shutdown-17\" width=\"600\" height=\"384\" \/><\/p>\n<p>Using the <strong>command line<\/strong>, SSH the ESXi by entering the <em>root<\/em> credentials and run the following ESXCLI command:<\/p>\n<p><span style=\"color: #0000ff;\"># esxcli system maintenanceMode set -e true -m noAction<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24109 size-large\" title=\"vsan-cluster-shutdown-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-18-600x42.jpg\" alt=\"vsan-cluster-shutdown-18\" width=\"600\" height=\"42\" \/><\/p>\n<p>The ESXi host is now in Maintenance Mode.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24110 size-large\" title=\"vsan-cluster-shutdown-19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-19-600x211.jpg\" alt=\"vsan-cluster-shutdown-19\" width=\"600\" height=\"211\" \/><\/p>\n<p>ESXi hosts can be shutdown or rebooted.<\/p>\n<p>&nbsp;<\/p>\n<h2>Power on the vSAN cluster<\/h2>\n<p>To power on the vSAN cluster, using the vSphere Host Client connect to each ESXi and right click <strong>Host<\/strong> then select <strong>Exit maintenance mode<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24111 size-full\" title=\"vsan-cluster-shutdown-20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-20.jpg\" alt=\"vsan-cluster-shutdown-20\" width=\"444\" height=\"458\" \/><\/p>\n<p>Alternatively run from the shell the ESXCLI command:<\/p>\n<p><span style=\"color: #0000ff;\"># esxcli system maintenanceMode set -e false<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24112 size-large\" title=\"vsan-cluster-shutdown-21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-21-600x45.jpg\" alt=\"vsan-cluster-shutdown-21\" width=\"600\" height=\"45\" \/><\/p>\n<p>Do the same for the other hosts members of the vSAN cluster.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24113 size-large\" title=\"vsan-cluster-shutdown-22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-22-600x46.jpg\" alt=\"vsan-cluster-shutdown-22\" width=\"600\" height=\"46\" \/><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24114 size-large\" title=\"vsan-cluster-shutdown-23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-23-600x48.jpg\" alt=\"vsan-cluster-shutdown-23\" width=\"600\" height=\"48\" \/><\/p>\n<p>Connect to the first ESXi host and <strong>power on your vCenter Server<\/strong>\u00a0and the Domain Controller as well in case you use Active Directory. It may take a few minutes for vCenter Server to become available again. The green icons in the column <strong>Status<\/strong> indicate the VMs are reacheable then the vSAN datastore is available.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24115 size-large\" title=\"vsan-cluster-shutdown-24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-24-600x264.jpg\" alt=\"vsan-cluster-shutdown-24\" width=\"600\" height=\"264\" \/><\/p>\n<p>When you are able to connect to the vSphere Web Client, do a <strong>quick health check on the vSAN cluster<\/strong>\u00a0to ensure the vSAN cluster is running with no errors.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24116 size-large\" title=\"vsan-cluster-shutdown-25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-25-600x295.jpg\" alt=\"vsan-cluster-shutdown-25\" width=\"600\" height=\"295\" \/><\/p>\n<p>If everything is fine, power on the <strong>remaining virtual machines<\/strong> in the vSAN cluster.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-24117 size-large\" title=\"vsan-cluster-shutdown-26\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/03\/vsan-cluster-shutdown-26-600x399.jpg\" alt=\"vsan-cluster-shutdown-26\" width=\"600\" height=\"399\" \/><\/p>\n<p>This procedure must be <strong>used only<\/strong> when you need to shutdown the <strong>entire vSAN cluster<\/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>To shutdown the vSAN cluster with vCenter running on the datastore, you need to follow a specific procedure to avoid data loss\u00a0keeping the cluster configuration healthy. In addition, if the vCenter Server Appliance (vCSA) is stored in the vSAN cluster, you need to follow a specific sequence to properly shutdown the running VMs.<\/p>\n","protected":false},"author":3,"featured_media":23821,"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":{"facebook_2879994398731222_17841400390232720":"","mastodon_115463926174894442_115463926174894442":"","linkedin_93tdZWzMZc_93tdZWzMZc":"","bluesky_did:plc:tkabz5kl2rukzdwtuongv3kz_did:plc:tkabz5kl2rukzdwtuongv3kz":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,1853],"tags":[28,169,1664],"class_list":["post-23820","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsan-en","tag-cluster","tag-shutdown","tag-vsan","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/23820","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=23820"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/23820\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/23821"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=23820"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=23820"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=23820"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}