The consolidation may take a few minutes and the VM performance may degrade.Īfter that the warning of the VM consolidation will disappear. Then vCenter will consolidate disks and clear the logs.
Are you sure you want to continue?Ĭonfirm that you want to delete the redundant logs. This operation consolidates all redundant redo logs on your virtual machine. To fix the error ‘Virtual machine Consolidation Needed’, right-click on the virtual machine and select VM -> Snapshots -> Consolidate.Ī window with the following request appears:Confirm Consolidate Connection problems (possibly temporary) between the vCenter server and the ESXi host.Make sure that there are no running processes of a virtual machine backup vSphere or a third-party app (as a rule, it is a backup application, like HP DataPtotector, Veeam or Netapp VSC) has locked snapshot files.There is not enough space on the VMFS store to perform consolidation.Poor storage performance, due to which snapshots cannot be deleted/consolidated due to a timeout or a large size of a snapshot.The most typical causes of the ‘Virtual Machine disks consolidation is needed’ error are: This causes a virtual machine backup errors. The warning ‘ Virtual Machine disks consolidation is needed’ in the Summary tab of a virtual machine in the VMware vSphere console means that when deleting a snapshot (using the option Delete or Delete All), the snapshot VMDK files or logs have not been deleted correctly (remain on the storage). Be careful here, selecting just “Remove from Virtual Machnie”, and don’t delete files from disk! – Select Hard Disk 2 (the extra hard disks) and click “Remove”. Remove all hot-added disks from the Veeam VM.If the Virtual Appliance mode failed to unmount hot-added disks: This should clear the snapshot(s) present.Note: This may cause a temporary “stun” period, so take necessary maintenance precautions if necessary. Restart the management agents on that host.If the VMware host held a lock on that snapshot.Virtual Appliance mode failed to unmount hot-added disks, which prevents the snapshot from being commited.The VMware host held a lock on that snapshot, typically due to a communication error between Veeam and the host/VC.
0 kommentar(er)
