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

VMware vCenter Site Recovery Manager may not correctly cleanup snapshot LUNs (2017655)

  • 2 Ratings


  • After an SRM cleanup task, the snap volume is still showing in vCenter Server.
  • On the ESXi host, an APD issue is detected:

    naa.60a9800050334f516d4a694d6a53666e : NETAPP Fibre Channel Disk (naa.60a9800050334f516d4a694d6a53666e)
       vmhba3:C0:T0:L0 LUN:0 state:dead fc Adapter: Unavailable Target: Unavailable

  • In the vmkernel.log file, you see entries similar to:

    vmkernel: 13:01:17:39.538 cpu4:4115353)ScsiDevice: 2310: Can't unregister device naa.60a9800050334f516d4a694d6a53666e because it is in use. OpenCount:1 RefCount:2 FilterCount:0
    vmkernel: 13:01:17:39.538 cpu4:4115353)WARNING: NMP: nmp_DeviceUnregister: Could not unregister NMP device "naa.60a9800050334f516d4a694d6a53666e". Busy

  • In the SRM logs, you see entries similar to:

    [01484 warning 'StorageProvider' opID=21E1C628-000000BF] Failed to Detach SCSI LUN 'naa.60a9800050334f516d4a694575306172' for host 'host-48:abzprdesx54.taqabratani.taqa1.local' - host does not support this operation.


SRM 5 tries to unmount and detach the VMFS volume to avoid any APD issues. However, this feature exists only in ESXi 5.x, and not in earlier versions.


There is no workaround for this issue.
To permanently resolve this issue, upgrade to ESXi 5.x.

Update History

11/30/2012 - Added link to article 1016626

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.


  • 2 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.
  • 2 Ratings