Plan and design your upgrade to be fail-safe. Before you attempt to upgrade Virtual SAN, verify that your environment meets the vSphere hardware and software requirements.
Consider the aspects that could delay the overall upgrade process. For guidelines and best practices, see the vSphere Upgrade documentation.
|Software, hardware, drivers, firmware, and storage I/O controllers||Verify that the software and hardware components, drivers, firmware, and storage I/O controllers that you plan on using are supported by Virtual SAN for 6.5 and later, and are listed on the VMware Compatibility Guide Web site at http://www.vmware.com/resources/compatibility/search.php.|
|Virtual SAN version||Verify that you are using the latest version of Virtual SAN. If you are currently running a beta version and plan on upgrading Virtual SAN to 6.5, your upgrade will fail. When you upgrade from a beta version, you must perform a fresh deployment of Virtual SAN.|
|Disk space||Verify that you have enough space available to complete the software version upgrade. The amount of disk storage needed for the vCenter Server installation depends on your vCenter Server configuration. For guidelines about the disk space required for upgrading vSphere, see the vSphere Upgrade documentation.|
|Virtual SAN disk format||Verify that you have enough capacity available to upgrade the disk format. If you do not have free space equal to the consumed capacity of the largest disk group, with the space available on disk groups other than the disk groups that are being converted, you must choose Allow reduced redundancy as the data migration option.
For example, the largest disk group in a cluster has 10 TB of physical capacity, but only 5 TB is being consumed. An additional 5 TB of spare capacity will be needed elsewhere in the cluster, excluding the disk groups that are being migrated. When upgrading the Virtual SAN disk format, verify that the hosts are not in maintenance mode. When any member host of a Virtual SAN cluster enters maintenance mode, the cluster capacity is automatically reduced, because the member host no longer contributes storage to the cluster and the capacity on the host is unavailable for data. For information about various evacuation modes, see the Place a Member of Virtual SAN Cluster in Maintenance Mode.
|Virtual SAN hosts||Verify that you have placed the Virtual SAN hosts in maintenance mode and selected the Ensure Accessibility or Full data migration option.
Ensure Accessibility. When you use the Ensure Accessibility mode, your data is not completely protected, and if you encounter a failure while upgrading Virtual SAN, you might experience unexpected data loss. However, the Ensure Accessibility mode is faster than the Full data migration mode, because you do not need to move all data to another host in the cluster. For information about various evacuation modes, see the Place a Member of Virtual SAN Cluster in Maintenance Mode.However, when you use vSphere Update Manager to upgrade Virtual SAN, the default evacuation mode is
|Virtual Machines||Verify that you have backed up your virtual machines.|
- If ESXi hosts are configured with memory capacity of 512 GB or less, use SATADOM, SD, USB, or hard disk devices as the installation media.
- If ESXi hosts are configured with memory capacity greater than 512 GB, use a separate magnetic disk or flash device as the installation device. If you are using a separate device, verify that Virtual SAN is not claiming the device.
- When you boot a Virtual SAN host from a SATADOM device, you must use a single-level cell (SLC) device and the size of the boot device must be at least 16 GB.