Skip to main content
NetApp Knowledge Base

VMware vSphere: Unable to restore VM's from .snapshot directory

  1. Last updated
  2. Save as PDF
Views:
925
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
virt
Last Updated:

Applies to

VMware vSphere 6.7U3 

Issue

NetApp ONTAP stores volume snapshots in a .snapshot directory within the volume. 

  • This .snapshot directory, if made visible from ONTAP, can be browsed via the storage view in the vSphere WebClient or UI client
  • Customers can browse the .snapshot directory to restore files that they need from a NetApp volume snapshot

There is an issue seen in vSphere 6.7U3 when CBT (Changed Block Tracking) is enabled.  The symptoms of this issue are:

  • Customers cannot copy vmdk / -flat.vmdk files from the .snapshot directory via the vSphere UI or by cloning using vmkfstools -i
  • When attempting to clone or copy a vmdk / -flat.vmdk file from the .snapshot directory, the following error is encountered:

DISKLIB-LIB_CLONE   : Failed to clone : Invalid change tracker error code (5948)

-or-

2019-10-11T16:44:55.855Z info hostd[2100574] [Originator@6876 sub=DiskLib opID=esxui-abcd-1234 user=root] DISKLIB-CTK : Could not open change tracking 
 file "/vmfs/volumes/abcd123-abcd123
/.snapshot/daily.2019-10-11_0010/VM/VM-ctk.vmdk": Change tracking invalid or disk in use.

  • When CBT is disabled, and there is no -ctk.vmdk file, the copy operation is successful.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.