Last time I described how to build test environment for vSAN 5.5 on one physical server. Today I want try to update VMWare vSAN 5.5 to vSAN 6.0. After that I will upgrade vSAN in Production.
So we have our test environment with nested esxi virtual hosts. We have updated hosts and vCenter to 6.0. And see notification on our vSAN cluster.
There are four steps to the upgrade process:
- Upgrading vCenter Server to 6.0
- Upgrading the ESXi hosts to 6.0
- Upgrading the on-disk filesystem format from v1 to v2 (VMFS-L to VirstoFS)
- Upgrading the components to v2
Items 1 & 2 are outside the scope of this post. I think you can do it without any issues. The second thing to consider is how many nodes are in your VSAN cluster. Is it 4 or more, or just 3 nodes? Different options to the command need to be used to upgrade the on-disk format depending on the configuration. We will work with 3 nodes configuration.
From official documentation:
3 node cluster (or insufficient resources).
So lets start to upgrade the Virtual SAN Disk Format.
1. Log in to your RVC tool.
2. Run the vsan.disks_stats /< vCenter IP address or hostname>/<data center
name>/computers/<cluster name> command to view the disk status.
The command lists the names of all devices and hosts in the Virtual SAN cluster. The command also displays the current disk format and its health status. You can also check the current health of the devices in the Health Status column from the Disk Management page. For example, the device status appears as Unhealthy in the Health Status column for the hosts or disk groups that have failed devices.
3. Run the vsan.v2_ondisk_upgrade <path to vsan cluster> command .
For 3 node clusters, and for clusters that do not have the available capacity to do an evacuation of each disk group, the on-disk format can still be upgraded to v2. However the VMs will be unprotected for the duration of the upgrade. If you attempt to upgrade the on-disk format to v2, and there are not enough resources in the cluster, it will fails.
An option will need to be added to the upgrade command called –allow-reduced-redundancy to allow the on-disk format to be upgraded:
vsan.v2_ondisk_upgrade <cluster> –allow-reduced-redundancy
This method will not evacuate data to the other hosts in the cluster. This option will simply remove disk group(s), and add the disks back to a v2 format disk group. This is the process it uses:
4. Monitor the progress in RVC and Web-client
RVC upgrades one disk group at a time.
Objects will have components going into a degraded state as part of this upgrade process.
This is normal, and the components of the objects will be resynchronized as soon as the on-disk format is upgraded. This can take a bit of time if there are lots of components to resynchronize.
After the disk format upgrade has completed successfully, the following message appears.
5. Run the vsan.obj_status_report command to verify that the object versions are upgraded from 1.0 to
Verify the Virtual SAN Cluster Upgrade
The Virtual SAN cluster upgrade is not complete until you have verified that you are using the latest version of vSphere and Virtual SAN is available for use. After you finish upgrading the disk format, you must verify whether the Virtual SAN cluster is using the new on-disk format.
1. Browse to the Virtual SAN cluster in the vSphere Web Client navigator.
2. Click the Manage tab and click Settings > Virtual SAN > Disk Management.
The disk format version that you are using appears in the Disk Format Version column. For example, if you are using disk format 1.0, it appears as version 1 in the Disk Format Version column. For on-disk format 2.0, the disk format version appears as version 2.
There is a detailed step-by-step upgrade process in the VSAN 6.0 Administrator’s Guide. Strongly recommended to read it before start. Also some possible issues in the VSAN 6.0 Troubleshooting Reference Manual.