{"id":35089,"date":"2018-10-25T09:00:56","date_gmt":"2018-10-25T07:00:56","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=35089"},"modified":"2023-07-16T11:30:31","modified_gmt":"2023-07-16T09:30:31","slug":"vsphere-6-7-upgrade-vsan-6-6-to-6-7-pt-4","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-vsan-6-6-to-6-7-pt-4\/","title":{"rendered":"vSphere 6.7 upgrade vSAN 6.6 to 6.7 - pt.4"},"content":{"rendered":"

\"vsphere-67-upgrade-vsan-01\"<\/p>\n

If the virtual infrastructure in use is configured with vSAN, after completing the upgrade of both vCSA and ESXi hosts to version 6.7, also vSAN should be upgraded to latest version.<\/p>\n

After the upgrade of vSphere components (vCSA and ESXi hosts), the vSAN cluster's Summary<\/strong>\u00a0tab displays a warning message related to Disk format version<\/strong>.<\/p>\n

\"vsphere-67-upgrade-vsan-02\"<\/p>\n

This warning is due to vSphere 6.7 that comes with the new vSAN version 6.7<\/a>.<\/p>\n

 <\/p>\n

Blog Series<\/h2>\n

vSphere 6.7 install vCSA - pt.1<\/a>
\nvSphere 6.7 upgrade vCSA 6.5 to 6.7 - pt.2<\/a>
\nvSphere 6.7 upgrade ESXi 6.5 to 6.7 - pt.3
\nvSphere 6.7 upgrade vSAN 6.6 to 6.7 - pt.4<\/p>\n

 <\/p>\n

vSAN cluster checks before the upgrade<\/h2>\n

Before upgrading the vSAN cluster, some checks must be performed<\/strong> to avoid possible issues or data loss during the upgrade process.<\/p>\n

Select the vSAN cluster and go to Configure<\/strong> tab. Click on Disk Management<\/strong> under vSAN<\/strong> area and verify that vSAN Health Status<\/strong> is reported as\u00a0Healthy<\/strong> for all disks and disk groups configured.<\/p>\n

\"vsphere-67-upgrade-vsan-03\"<\/p>\n

Make sure that no rebuilding tasks<\/strong> are currently running in the vSAN cluster. From vSphere Client select the vSAN cluster and go to Monitor<\/strong> tab. Select Resyncing Objects<\/strong> option under vSAN<\/strong> section. In this area you can check running tasks or perform a synchronization<\/strong> before proceeding with the upgrade by clicking Resync Throttling<\/strong>.<\/p>\n

\"vsphere-67-upgrade-vsan-04\"<\/p>\n

From vSphere Client select the vSAN cluster and go to Configure<\/b>\u00a0tab. Click Pre-Check Upgrade<\/strong> button before launching the upgrade to ensure vSAN can be safely upgraded.<\/p>\n

\"vsphere-67-upgrade-vsan-05\"<\/p>\n

If the Pre-Check Upgrade process reports a green flag<\/strong> with Ready to upgrade - pre-check completed successfully<\/strong>, the system is ready to be upgraded.<\/p>\n

\"vsphere-67-upgrade-vsan-06\"<\/p>\n

 <\/p>\n

Upgrade vSAN<\/h2>\n

When the pre-checks have been completed, from Configuration<\/strong> tab select Disk management<\/strong> option under vSAN<\/strong> section. Click Upgrade<\/strong> button to perform the upgrade of your vSAN cluster.<\/p>\n

\"vsphere-67-upgrade-vsan-07\"<\/p>\n

Based on your requirements select the Allow Reduced Redundancy<\/strong> option.<\/p>\n

\"vsphere-67-upgrade-vsan-08\"<\/p>\n

Click\u00a0Upgrade<\/strong>\u00a0to proceed with the upgrade.<\/p>\n

\"vsphere-67-upgrade-vsan-09\"<\/p>\n

The upgrade takes place and requires some minutes to complete depending on the disks size<\/strong>.<\/p>\n

\"vsphere-67-upgrade-vsan-10\"<\/p>\n

When the upgrade process has been completed successfully, the system reports a green flag with the status All <disks_number><\/em>\u00a0disks on version 6.0<\/strong>.<\/p>\n

\"vsphere-67-upgrade-vsan-11\"<\/p>\n

\"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

If the virtual infrastructure in use is configured with vSAN, after completing the upgrade of both vCSA and ESXi hosts to version 6.7, also vSAN should be upgraded to latest version. After the upgrade of vSphere components (vCSA and ESXi hosts), the vSAN cluster's Summary\u00a0tab displays a warning message related to Disk format version.<\/p>\n","protected":false},"author":3,"featured_media":35520,"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":[876,1664,1879],"class_list":["post-35089","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-upgrade-en","tag-vsan","tag-vsphere-6-7","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35089","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=35089"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35089\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/35520"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=35089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=35089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=35089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

The procedure to upgrade vSAN is now complete.\u00a0The virtual infrastructure is now running vSphere 6.7 and you are able to take benefit of new features provided<\/a>.<\/p>\n