Upgrade the VMware vSAN disk format on an AMP-VX cluster About this task Upgrade the VMware vCenter Server, VMware ESXi hosts, and the vSAN disk format, in that order, to upgrade the AMP-VX cluster. CAUTION: Failure to follow the sequence of upgrade tasks may lead to data loss and cluster failure. Before you begin Ensure you have a full backup of all data that is stored on the vSAN. Ensure that enough free space is available. The space available must equal the logical consumed capacity of the largest disk group. You need a separate disk group with the available capacity from the one you are migrating. Verify that the disks are in a healthy state. Go to the Disk Management page to verify the object status. Once you upgrade the on-disk format, you cannot roll back software on the hosts or add certain older hosts to the cluster. See About the vSAN Disk Format Procedure Go to the VMware vSAN cluster. Select the Configure tab. Under vSAN, select Disk Management. Click Pre-check Upgrade. NOTE: The upgrade precheck analyzes the cluster to uncover any issues that might prevent a successful upgrade. Some of the items that are checked are host status, disk status, network status, and object status. Upgrade issues are displayed in the Disk pre-check status text box. Click Upgrade. The disk groups are upgraded one at a time. For each disk group upgrade, all data from each device is evacuated and the disk group is removed from the vSAN cluster. The disk group is then added back to vSAN with the new on-disk format. WARNING: While the upgrade is in progress, do not remove or disconnect any host, and do not place a host in maintenance mode. When any member host of a vSAN cluster enters maintenance mode, the member host no longer contributes capacity to the cluster. The cluster capacity is reduced, and the cluster upgrade might fail. Click Yes on the Upgrade dialog box to perform the upgrade of the on-disk format. See Upgrade vSAN Disk Format Using vSphere Client Parent topic Upgrade to VMware vSphere 7.0Some VxBlock System components are optional or specific to environments. If you do not have a specific component, skip that component. When the component is in a cluster configuration, upgrade the subordinate component before you upgrade the primary component.