![]() ![]() In VMware KB 1007566 “Commands to monitor snapshot deletion in ESX 2.5/3.x/4.x and ESXi 3.x/4.x/5.x (1007566)” some very useful commands are presented to watch the progress of the consolidation process, especially this command is good for the job: Now, return to the vSphere Client and restart the Consolidation. SSH to the ESXi server and CD to the folder where the affected VM resides and create a temporary folder: Select the ESXi host, Configuration, Software, Security Profile, under Services, start the SSH service). The first step is to SSH to the console of the ESXi host (in most situations, you will need to relax the security settings while working on this issue). CTK files to the newly created folder and try to consolidate the snapshots. The presented resolution is to create a temporary folder, move the. Time to check the vmware.log file of the virtual machine.Īs the KB article already suggest, the tracking files (CTK files) are not accessible (Could not open/create change tracking file). No panic, another KB will help you KB 2013520 “Committing or creating snapshots fail with the error: the virtual disk is either corrupted or not a supported format”. So far so good, but some moments later, a new message was received and the consolidation task was ended. ![]() Right-click the virtual machine and from the menu, choose Snapshot > Consolidate. VMware KB 2003638 “Consolidating snapshots in vSphere 5.x” details the backgrounds for this message and also presents a solution for resolving this issue. At the end of the day the snapshot was deleted. Virtual machine disks consolidation is needed”.Ī few days before, a snapshot was made as part of a regular update process. ![]() One morning while reviewing a vSphere 5.1 cluster at a customer location, I noticed one VM with the following message “Configuration Issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |