VMWARE 4.1 ESXi Cloning process – issues

Home Forums Virtualization VMware Virtualization VMWARE 4.1 ESXi Cloning process – issues

This topic contains 8 replies, has 7 voices, and was last updated by Avatar Spot 7 years ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • Avatar
    sharkitus
    Member
    #158105

    Hello all, I am still fairly new to the VMware environment so please forgive me if I am not using some of these terms correctly. I inherited this system from our previous IT manager and we are just trying to get it under control.

    OS – VMware 4.1 ESXi

    We have a VM SQL server that has a few critical applications on it. I noticed that someone left a snapshot attached that has grown to 475GB while the VM itself is only 110 GB max.

    After doing a little research simply deleting the snapshot is no longer a viable option as per VMware’s website and multiple online articles. Trying to delete a snapshot of this size could hang the system for a week or worse.

    The option we came up with is to try and clone the system without the snapshot attached. When we try this we get an error “insufficient disk space”. We have almost 400GB available space for a 110GB VM. So I am assuming the host is seeing the snapshot and trying to do something with it.

    Is there a way to clone the VM an NOT have it take into account the attached snapshot?

    If so, how?
    If Not, does anyone have a good solution to get out of this mess?

    Avatar
    TigaFan09
    Member
    #379430

    Re: VMWARE 4.1 ESXi Cloning process – issues

    Oh dear, that’s not a good situation…

    One option I’ve seen people take in that kind of situation is to transfer the software and data into a new VM, effectively performing a P2V operation. VMware Converter can be used to do this, make it think it’s converting a physical machine – if you’ve used Converter before you should know the process to follow.

    I would definitely stop SQL services during that process, to ensure you can a consistent data transfer into the new VM. Once complete and tested, you simply delete the old VM.

    Avatar
    Dumber
    Participant
    #201821

    Re: VMWARE 4.1 ESXi Cloning process – issues

    The option Scott mentioned is the only option I could think of it as well.

    Avatar
    kyengineer
    Member
    #375191

    Re: VMWARE 4.1 ESXi Cloning process – issues

    Thanks guys we will be giving it a try this morning. I’ll let you guys know how it works out.

    Avatar
    m80arm
    Member
    #234070

    Re: VMWARE 4.1 ESXi Cloning process – issues

    The guy before me used snapshots as a backup strategy whereby he would take one every month just in case. When I took over I deleted then but the process failed / timed out after a while in the gui but the process still ran in the background. It wasn’t the size that you have to deal with and the solution Scott put forward is definitely your best good.

    Good luck

    Avatar
    Maish
    Member
    #326176

    Re: VMWARE 4.1 ESXi Cloning process – issues

    The only other thing I can think of – albeit not optimal is to mount put a desktop with a Linux distro with a big enough disk – and export an NFS share.

    Mount that NFS share to your ESX box – and clone the VM to there.

    Avatar
    kyengineer
    Member
    #375192

    Re: VMWARE 4.1 ESXi Cloning process – issues

    scott28tt;255481 wrote:
    Oh dear, that’s not a good situation…

    One option I’ve seen people take in that kind of situation is to transfer the software and data into a new VM, effectively performing a P2V operation. VMware Converter can be used to do this, make it think it’s converting a physical machine – if you’ve used Converter before you should know the process to follow.

    I would definitely stop SQL services during that process, to ensure you can a consistent data transfer into the new VM. Once complete and tested, you simply delete the old VM.

    Worked like a charm, Thanks Scott. We scheduled some down time and shut down the server to be safe. Worked out nicely and we recovered all of the free space.

    Avatar
    TigaFan09
    Member
    #379434

    Re: VMWARE 4.1 ESXi Cloning process – issues

    sharkitus;256445 wrote:
    Worked like a charm, Thanks Scott. We scheduled some down time and shut down the server to be safe. Worked out nicely and we recovered all of the free space.

    That’s great news :-)

    Avatar
    Spot
    Member
    #386130

    Re: VMWARE 4.1 ESXi Cloning process – issues

    I would the last version of the VMWARE standalone converter and use it installing it directly on the server that you want to convert to virtual…

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.