Search the VMware Knowledge Base (KB)
View by Article ID

Snapshot LUN detection in ESX and ESXi (1011385)

  • 29 Ratings


This article highlights the differences in snapshot LUN detection between ESX 3.x and ESX/ESXi 4.x and 5.x.


How a LUN is detected as a snapshot in ESX 3.0.x
When an ESX 3.x server finds a VMFS-3 LUN, it compares the SCSI_DiskID information returned from the storage array with the SCSI_DiskID information stored in the LVM Header.
If the two IDs do not match, the VMFS-3 volume is not mounted.
A VMFS volume on ESX 3.x can be detected as a snapshot for a number of reasons:
  • LUN ID change
  • SCSI version supported by array changed (firmware upgrade)
  • Identifier type changed – Unit Serial Number vs NAA ID
How a LUN is detected as a snapshot in ESX/ESXi 3.5.x and later.
When trying to determine if a device is a snapshot in ESX/ESXi 3.5 and later releases, the ESX/ESXi host uses a globally unique identifier to identify each LUN, typically the Network Addressing Authority (NAA) ID.
NAA IDs are unique and are persistent across reboots.
There are many different globally unique identifiers. If the LUN does not support any of these globally unique identifiers, ESX falls back to the serial number + LUN ID used in ESX 3.x.

See Also

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.


  • 29 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 29 Ratings