Then go to ESXi host shell console and do the following tasks:įirst, let’s list all ctk ls -l *ctk.vmdk Sometimes all that is necessary is to remove all these ctk files and delete all Snapshots or Consolidate the disks, and this will fix the problem.Ī faster and safe way is to move (not delete) all ctk files to a temp folder and try to delete all Snapshots.įirst, you need to power off the VM. So after this, I suspected that was an issue originated by Veeam Backup tool. So that Backup tools only backup the altered disk sectors since the last changed ID (or backup). What are ctk files? CTK files are used by Changed Block Tracking (CBT) to track disk sectors that have been changed since the last backup. This is not a reasonable number of snapshots and not a reasonable number of ctk files. Note: Since this issue happen in my vCenter DB and vCenter was down, I had to connect with vSphere Client to the ESXi host directly where this VM was allocated ( if this issue is in any of your vCenter VMs, you should check which ESXi host is the VMS using, before power off the vCenter).īrowsing the Datastore where the VM is located and in the VM folder, I found 18 Snapshots files and 18 ctk vmdk files. With this message, this issue needs further troubleshooting. When trying to consolidate (with VM power down) the disks, I get: “An error occurred while consolidating disks: -DISKLOCKED”. Sometimes is needed to power off the VM so that all vmdk locks are free and VM can consolidate all snapshots. All we need to do is click in the VM and the “Snapshot – Consolidate” option we can fix this issue. Today one of our vCenter DB VMs we had a warning with the following message: “Virtual Disk Consolidation is required.” This is normal in a VMware farm and happens sometimes (this could be caused by too many snapshot, very old snapshots or snapshot that were not properly removed).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |