[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1777
  • Last Modified:

VMware ESXi - REDO files / Snapshots - Server has run out of space please explain / help

Hi there,

I have an ESXi box that was configured - we had created a couple of snapshots over the past month just as we were setting up the box - the other night the server ran out of space even though there should have been about 150gb of free space.

Once we managed to get into it we noticed that there was a file about 130gb big with filename000XX.vmdk in the datastore but it was for the date the server crashed. We did not create a snapshot.

We had an error in the events saying not enough room for redo file.

What is this redo file / how does it work.

I read if I delete these files I lose data unless I commit the data so how do i do that.

How can I prevent this happening going forward.

I really appreciate any help people can give.

Michael
0
mickinoz2005
Asked:
mickinoz2005
1 Solution
 
kumarnirmalCommented:
When creating a Virtual Hard Disk you have 4 Options, Persistent, Non Persistent, Undoable and Append.

Persistent would commit all data to the VMDK File when the VM is shutdown

Non Persistent would erase all data to the VMDK File when VM is shut down

Undoable provides the user the ability to either commit or delete the data when shutting down the VM

Append would commit the changes to REDO File which can be deleted to restore the VM back to original position or committed for the changes to take effect.

The best way of recovering this VM is to use VMware vConverter 4.0 and clone the VM to a new destination.
0
 
mickinoz2005Author Commented:
That is the thing i read what you said above but when we go to create a vm on the ESXi box we only have the option for Persistent and Non Persistent - there is a tick box for Independent Disks and when you tick it these two options become available but non of the others are there.

0
 
robocatCommented:

The comments about disk modes are outdated and in ESXi this has been replaced by snapshots.

Use the snapshot menu in the VI client to see if there are any snapshots associated with this VM. Delete (=commit)  them if you find any. If you see no snapshots, try creating one and see if any others appear.

If you have no disk space left at all, you may find that deleting snapshots is impossible. If this is the case you're in real trouble and you'll need to find a way to create some free space.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now