Today I got some problems with backing up one of my VM’s using VMware Data Recovery. I was looking what was going wrong after a few failures.. And yes.. hanging snapshots
Trying to remove the snapshots was a little bit different. When I went into the “Snapshot Manager” there were no active snapshots and I couldn’t delete the files. But while browsing the Datastore I saw many active snapshots.
– You can “Revert to Current Snapshot” via menu..
– But.. in the “Snapshot Manager” I didn’t see the active snapshots and my options were grayed out.
– Browsing the Datastore there are many active snapshots..
Resolve the issue: Option 1
– Create a new snapshots in the menu, call it “Test”;
– Goto Snapshot Manager. You can now see the “Consolidate Helper –0” as active snapshot + my own created snapshot: “test”
– Select your “Test” snapshot and press “Delete All”
Hopefully your problem is solved 🙂
Resolve the issue: Option 2
Of course in my case it didn’t solve my problem, I received this errors:
Unable to access file <unspecified filename> since it is locked
A general system error occurred: Protocol error from VMX.
This problem occurred after creating a backup with VMware Data Recovery, so I decided to check my Data Recovery logs and VM settings. After checking my VM settings I saw Hard disk 2. I thought I’d never added a second disk on this VM?
– Hard Disk 2 = Disk file location [SAN OS] SDENERGIE01/SDENERGIE01_1.vmdk
– Hard Disk 2 = Independent
– Hard Disk 2 = Also mounted on “SDENERGIE01” VM
So the only explanation was that the disk is also mounted on a second VM as a Independent disk. That is why I received “Unable to access file <unspecified filename> since it is locked”.
– Power Off the VMware Data Recovery VM
– Select Hard Disk 2 (the extra hard disks) and click “Remove”. Be careful here, selecting just “Remove from Virtual Machnie”, and don’t delete files from disk!
– Power On “VMware Data Recovery” VM
– Repeat solution Option 1 (^ above)
Problem solved. My Datastore is snapshot free without any downtime 🙂