![]() ![]() This tends to be caused by limited resources on the vCenter server (specifically RAM) however can be caused by the vCenter and/or Rapid Recovery core rebooting during the course of an agent-less backup. vmdks mounted to other VMs or perhaps other snapshot anomalies are afoot however this is the most common culprit with an agent-less backups solution active in the environment. ![]() Once the snapshots are deleted the error message should disappear.Once removed right click the VM with the error in vSphere again and go to Snapshot > Snapshot Manager and click ‘Delete All’.Find the hard disk that references the VM that is getting the disk consolidation error and Remove the disk (DO NOT remove and delete, just remove from virtual machine).Right click the VM that is running the Rapid Recovery core, and go to Edit Setting.Do a non-memory and a non-quiesced snapshot of the VM (the name does not matter, but you do have to name it something).Right click the VM and go to Snapshot > Take a Snapshot.Open up vSphere and right click the VM that is having the disk consolidation errors.The way that you DO resolve this situation is as follows: (if you do run across this error the Consolidate option from the snapshot menu in VMware will not fix this) Storage Performance and Utilization Management.Information Archiving & Storage Management.Hybrid Active Directory Security and Governance. ![]() Starling Identity Analytics & Risk Intelligence.One Identity Safeguard for Privileged Passwords. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |