VMware Cloud Community
Archparks2
Enthusiast
Enthusiast

Stuck temporary snapshot (created by Veeam Quick Migration) - how to get rid of it?

This past weekend, I ran the VEEAM Quick migrate utility moving the VM from an NFS datastore to a local datastore. It got stuck at 99% but appeared to create the new VM machine. I started the VM and it is running fine and has been for almost a week. The datafiles on the old NFS datastore have not changed since Sunday thus there seems to be no interaction with those files.

I noticed that there is a snapshot called "Temporary snapshot for Veeam Quick Migration" on the new VM. When I try to delete then through Vcenter, I get this message:

Task Name,Target,Initiator,Queued For,Start Time,Completion Time,Server
Remove snapshot,VM2016,VSPHERE.LOCAL\\Admin,3 ms,7/18/2017 10:47:11 AM,7/18/2017 10:47:12 AM,vcenter.localdomain.com
"A general system error occurred: vim.fault.GenericVmConfigFault

I contacted VVEAM support. They said that, even though the stuck snap shot is a snapshot called "Temporary snapshot for Veeam Quick Migration" that was created by the Veeam Quick Migration it was not Veeam's problem. The explanation was "When we make the API call through the manage object browser Veeam can't see that snapshot 4. This causes a timeout on our side because the host is not reporting back anything about the snapshot. Like I said before we only make API calls for snapshot creation and consolidation. I would advise to reach out to VMware to get that taken care of. "

So...all that said, I'm still stuck with a stuck snapshot.

Anyone have any ideas?

Thanks!

0 Kudos
4 Replies
RvdNieuwendijk
Leadership
Leadership

You can try to create a new snapshot of the affected virtual machine and then click Delete All from the snapshot manager to consolidate all snapshots.

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
0 Kudos
dekoshal
Hot Shot
Hot Shot

Try out below kb article

Snapshot Manager fails to detect snapshots of VMs (1026380) | VMware KB

If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

Best Regards,

Deepak Koshal

CNE|CLA|CWMA|VCP4|VCP5|CCAH

0 Kudos
PFMarkeyRiley
Contributor
Contributor

I am waiting on a call from vmware for basically the same thing.

I believe my process just needs to do this:

https://www.veeam.com/kb1775

but I am waiting on an engineer, as this is exchange and our sql box!

0 Kudos
vijayrana968
Virtuoso
Virtuoso

On the new VM folder on  local datastore you will have vmname.vmsd file for this snapshot. Rename it to vmname.vmsd.old or something different.

Create a new snapshot > Then delete all from snapshot manager. This will commit new snapshot as well existing snapshot. Then delete any .vmsn or .vmsd files you find in VM folder as they are no longer usable.

0 Kudos