Having recently upgraded my home lab to ESXi 5.1, I’ve noticed that a number of VMs have stopped backing up via VDP. The symptoms were that the snapshot was created, the VDP job would reach 10%, then the snapshot would get removed and the job would fail.
After checking some logs, I noticed this error – E10055:failed to attach disk. Some investigation revealed KB article 2035736, but the solution there essentially involves disabling VSS, leaving only a file-system consistent backup. A number of my VMs run databases like MS SQL server or Exchange 2010, and turning off VSS was just asking for trouble.
Some searching for alternatives revealed this blog post, but some of the information there is not quite correct for Windows 2008 R2 virtual machines. So here’s what I did instead:
- remove the disk.EnableUUID entry in the vmx file, as per the vmware KB article 2035736
- create C:\windows\pre-freeze-script.bat
- create C:\windows\post-thaw-script.bat
The pre-freeze-script.bat contained these lines (add additional drive letters at the end of the last line):
echo Pre-Freezing at %date% %time% >> C:\vcb.log
vssadmin create shadow /For=C:
post-thaw-script.bat contained this (again, make sure to add any additional drive letters after C:):
echo Post-Thawing at %date% %time% >> C:\vcb.log
vssadmin delete shadows /For=C: /quiet
So now my VDP backups work, and they’re creating backups with an application-consistent backup. Perfect!
April 7, 2013 at 7:27 pm
This is **** crazy! VMware is **** expensive software and they are not able to get it work correctly with Windows.
July 3, 2013 at 6:29 pm
Thanks for the tips in your post. I have implemented this and whilst it does create a backup and I can access the files in the FLR recovery website, there are no VSS logs in the Application log and the Exchange log files are not truncated. Is this the behavior you saw also?
July 28, 2013 at 8:37 am
This issue is addressed in the latest version of VDP, so I highly suggest upgrading to that, removing the batch files and re-add the disk.EnableUUID option (which requires a restart of the VM to take effect).