Release 8.0U2b Available to Prevent Host Failure / Inaccessible Data Risk due to Rare Snapshot-related Condition on vSAN ESA (Version 8.0, 8.0U1, 8.0U1c)
search cancel

Release 8.0U2b Available to Prevent Host Failure / Inaccessible Data Risk due to Rare Snapshot-related Condition on vSAN ESA (Version 8.0, 8.0U1, 8.0U1c)

book

Article ID: 326659

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

This article provides information regarding a potential risk of host failure and inaccessible data, which is rare and specific to vSAN ESA. VMware publishes this KB to strongly recommend upgrading to 8.0U2 and beyond.

Symptoms:
The deletion of a snapshot in rare conditions may fail and result in a PSOD of the ESX host(s) and data inconsistency. This issue is specific to vSAN ESA clusters with versions 8.0, 8.0U1, and 8.0U1c releases only. vSAN OSA of those release versions doesn’t have this issue.

Environment

VMware vSAN ESA 8.0U1c and below

Cause

The likelihood of encountering this issue varies and primarily depends on the workload pattern and timing of snapshot creation. In rare cases, attempting to delete a snapshot may fail due to the snapshot being in an inconsistent state, leading to the PSOD of ESX host(s).

Resolution

Fix for this issue was first introduced in version 8.0U2b however Broadcom recommends upgrading vSAN ESA clusters to VMware-ESXi-8.0U3h-25067014 (80P07) and above as soon as possible as it's the most stable version and includes fixes & recovery tools for the below ESA snapshot issues.

Urgent Patch (8.0U1c) Available to Prevent Inaccessible Data Risk for VMs on vSAN ESA (Version 8.0, 8.0 P01, 8.0 U1, 8.0U1a (EP1))
vSAN -- ESA -- vSAN Critical Error -- Migration of VM’s with snapshots from a vSAN ESA 8.x Datastore may result in inconsistencies under certain specific conditions