Fail to Delete Old Basedisk on Vmware: Cannot delete file[VMStorage]****.vmdk

Fail to Delete Old Basedisk on Vmware: Cannot delete file[VMStorage]****.vmdk

book

Article ID: CTX464167

calendar_today

Updated On:

Description

Unable to delete basedisk after dedicated catalog update on vmware platform

Resolution

Delete all existing VDAs whose diff disk is linked to the old basedisk or modify the ddb.deletable flag in the basedisk vmdk file from false to true:
https://kb.vmware.com/s/article/2116782

Problem Cause

1. For Pool Random Machine Catalog update, the orphaned basedisk will be removed automatically by DDC background checking process, for details please refer to KB article:   
2. For Dedicate Machine Catalog(fast clone) update, the old basedisk will not be removed automatically by DDC cause it is still occupied by existing VDAs, only new provisioned VDAs will use new published basedisk:
  • For Citrix Hypervisor, VDA diff disk is linked to basecopy so old basedisk can be deleted manually after Machine Catalog Update   
a. Check the MCS Catalog ProvisioningSchemeId on DDC Powershell : 
        image.png

b. Locate basedisk from DB table [CitrixMiaoDDCSiteSite].[DesktopUpdateManagerSchema].[ProvisioningSchemeVMImageHistory] according to ProvisioningSchemeId:   

image.png 
 
c. Check VDA diff disk link from Citrix Hypervisor, only new provisioned VDAs use latest basedisk, existing VDAs will not be affected if old basedisk is removed because diff disk is directly linked to basecopy:
image.png
d. Rename old basedisk and delete it from XenCenter UI:
image.png
  • For VMware platform, VDA diff disk is linked to basedisk so existing VDAs will not boot up if old basedisk is deleted manually on VMware:
a. Check the MCS Catalog ProvisioningSchemeId on DDC Powershell and Locate basedisk from DB table [CitrixMiaoDDCSiteSite].[DesktopUpdateManagerSchema].[ProvisioningSchemeVMImageHistory] according to ProvisioningSchemeId:
image.pngimage.png
b. From VMware console the latest basedisk is created with highest digital marker after Machine Catalog Update:
image.png
c. We can check existing VDAs diff disk is still linked to the old basedisk and new provisioned VDAs diff disk is linked to the latest basedisk:
Existing VDA:
image.pngimage.png
New Provisioned VDA:
image.png
 
d. If we delete the old basedisk from Vmware console, it shows error:
            image.png 
e. Shutdown all existing VDAs linked to the old basedisk, modify the ddb.deletable flag from "false" to "true" in the basedisk vmdk file:
sed -i -e 's/deletable = "false"/deletable = "true"/' /vmfs/volumes/5b3ba00a-a28afafa-1063-1402ec96bf24/VMware-Dedicate-Win21H1-baseDisk-datastore-31/VMware-Dedicate-Win21H1-baseDisk-datastore-31.vmdk

Reference: https://kb.vmware.com/s/article/2116782
 
f. All existing VDAs will not boot up after old basedisk delete.
 
Powered by Wolken Software