vSAN1

 View Only
  • 1.  Snapshots VMDK files not deleted on vSAN Datastore

    Posted Jun 02, 2022 09:42 AM

    Hi,

    On a vSAN / vSphere 7 cluster, when I delete snapshots on a virtual machine, the deletion seems to work correctly but VMDK files are not deleted in the Datastore folder. As a result, the space consummed by the VM is very high, more than 2 TB for example (with FTT=1).

    Is there a way to delete these VMDK properly?

    Thanks



  • 2.  RE: Snapshots VMDK files not deleted on vSAN Datastore

    Posted Jun 02, 2022 09:45 AM

    do you have a screenshot of the files you see?



  • 3.  RE: Snapshots VMDK files not deleted on vSAN Datastore

    Posted Jun 02, 2022 11:04 AM

    Sure, here are the files located in the vSAN Datastore:

    ArnaudAxians_0-1654167593762.png

    This VM has only 3 snapshots.

    For information, after a Storage VMotion to another vSAN Cluster, I see a "considation needed status" message on the VM summary. I will try to consolidate to see if VMDK are properly deleted.



  • 4.  RE: Snapshots VMDK files not deleted on vSAN Datastore

    Posted Jun 02, 2022 05:02 PM

    According to the screenshot the VM does not have only 3, but 13 snapshots?

    Such issues often occur when a Hot-Add backup job fails to remove the mapped .vmdk file from its backup server/proxy. If that's the case, remove (don't delete) the mapped snapshot .vmdk from the backup server/proxy, and then run the consolidation, or "Delete All" from the Snapshot Manager.

    The above assumes, that you are not low on free disk space on the datastore, which is another common reason for failed snapshot consolidations.

    André



  • 5.  RE: Snapshots VMDK files not deleted on vSAN Datastore

    Posted Jun 03, 2022 07:42 AM

    Hi,

    Yes the VM has only 3 snapshots after all others have been deleted from the vSphere GUI.

    But in the Datastore browser (my screenshot) VMDK are still present.

    After the VM has been moved to another vSAN cluster, vCenter identifies the VMDK files and asks for a disks consolidation, and the consolidation merges correctly VMDK files. As as result the consumed space is drastically reduced.

    I asked the customer and he told me these VM are not backed up so, it can't be a failed backup job which would retain the VMDKs. And there is still a lot of free space on the vSAN Datastore.

    Thanks



  • 6.  RE: Snapshots VMDK files not deleted on vSAN Datastore

    Posted Jun 03, 2022 07:41 PM

    , don't just go by snapshot manager - validate what vmdks are currently part of the in-use disk-chain of the VM.

     

    This can be done by 1. identifying what vmdk is currently attached to the VM (either by checking it in 'Edit Settings' or by using cat on the vmx (only doable from the host where it is running)), then 2. use cat on this vmdk descriptor which will state what it's parent disk is, then do the same for that vmdk and so forth until the parent is just the base-vmdk.

     

    It may be the case that you have 13 vmdks but only 4 of them are in the active disk-chain and hence in use or it may be that you have 13 vmdks and 13 of them are part of the current disk-chain.