![]() ![]() ![]() Unfortunately, because you already tried to reconcile snapshots with insufficient disk space, there are no longer any. ![]() If this problem persists, you need to discard the RedoLog." The virtual machine needs to be powered off. When you try and power on the virtual machine in question, you will get the familiar: "The RedoLog for "SERVERNAME" has been detected to be corrupt. When you issue a delete all snapshots from the context menu of the Virtual Infrastructure (VI) client, if the disk space is insufficient to complete the operation, VMware has a nasty tendency to remove the physical snapshot files (.vmx) and leave you with a non-functional VM without any snapshots listed. Today I want to get a little more technical by talking about recovery options for virtual machines which will not boot because of snapshot errors. In my last entry, I discussed basic best practices for using snapshots in VMware environments. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |