Search the VMware Knowledge Base (KB)
View by Article ID
vSAN upgrade requirements (2145248)
Note: Depending on the desired target version, there may be intermediate steps required to ensure a smooth and effective upgrade process. Ensure you review the relevant section in detail.
Important considerations before you begin: Prior to beginning any vSAN upgrade process, please validate that the cluster is healthy:This table details the requirements to upgrade to any given version of vSAN. In general, the vSAN upgrade order is the same as the vSphere upgrade order, with the on-disk upgrade as the last step.
- All vSAN hosts are present, online, in a good state and manageable through vCenter Server
- There are no failed disks in any vSAN hosts
- There are no inaccessible objects in the vSAN cluster
- This can be checked using the vSAN Health Service in 6.0 and above
- This can be checked using the Ruby vSphere Console (RVC) in 5.5
|Target vSAN version||Minimum ESXi starting version||Post-upgrade on-disk format upgrade required?||Caveats|
|6.5 *||5.5, Express Patch 07||No, if upgrading from 6.2|
Yes, if upgrading from 6.0/6.1
Yes, if upgrading from 5.5
|Note: Issues resolved in the latest release of vSAN 6.2 (6.0 Patch 04) are not included in 6.5 GA.|
|6.2 *||5.5, Express Patch 07||Yes||6.2 is a significant vSAN release. Please ensure that all hardware is compliant per the vSAN Compatibility Guide|
|6.1||5.5, Express Patch 09||Yes, if upgrading from 5.5|
No, if upgrading from 6.0
|6.1 is a significant vSAN release. Please ensure that all hardware is compliant per the vSAN Compatibility Guide|
|6.0||5.5, Express Patch 09||Yes||6.0 is a vSAN major release. Please ensure that all hardware is compliant per the vSAN Compatibility Guide.|
|5.5, Update 2+||5.5, Update 1||No||Upgrade from 5.5 GA is not supported.|
- * Due to changes in vSAN 6.2 object handling, it is acceptable to migrate directly to 6.2 from earlier releases of 5.5, whereas it is not acceptable to migrate to 6.0 or 6.1 from those same earlier releases of 5.5.
- In vSAN 6.2, the required on-disk format upgrade may fail due to unassociated objects in the vSAN datastore or due to locking associated with changed-block tracking (CBT). For more information on resolving vSAN 6.2 on-disk upgrade failures, see the Additional Information section.
- If there is little available free space in the vSAN datastore or if the vSAN cluster has only three nodes or disk groups, the vSAN 6.2 on-disk upgrade may fail. If this occurs, a CLI alternative must be used. For more information, see KB 2144944 linked in the Additional Information section.
Version specific requirements:
vSAN 6.2 on-disk upgrade failures:
- VMware vSAN 6.2 on disk upgrade fails at 10% (2144881)
- VMware vSAN 6.2 on disk upgrade fails due to CBT enabled virtual disks (2144882)
- Upgrade of vSAN On-Disk Format from 2.5 to 3.0 with only one Disk Group per Host in a Stretched Cluster Fails with error "Out of resources to complete the operation" (2144944).
For more information about the vSphere upgrade process, including dependencies between ESXi and vCenter host versions, see:
- Update sequence for vSphere 6.0 and its compatible VMware products (2109760)
- VMware Product Interoperability Matrices
Note: If you need to identify your current update level by the build number, see Correlating VMware product build numbers to update levels (1014508).
- Upgrading from VMware vSphere 5.5 EP06 or 5.5 P04 to vSphere 6.0 GA can cause VMware vSAN Data Unavailability (2113024)
- Upgrading vSAN On-Disk format to 3.0 may fail in small vSAN clusters or ROBO/stretched clusters (2144944)
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.