Last week I had another interesting issue with backup exec.
As you can see from the title the job ended with a :
V-79-57344-34108 – An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
and another :
V-79-57344-65033 – Directory not found. Cannot backup directory D:\HOMEDIRS\BLA\Desktop and its subdirectories.
Needless to say that the directory ofcourse was available and backup ran fine like forever until then…
But first a little scenario of the problem:
-ESX 4 Host
-Windows 2008 R2 SP1 with shares on drive “D:”
-Backup of C: has no problem what so ever
-VSS errors filling up event log during backup of D:
So to isolate the problem I had checked every goddamn Symantec KB, every MS KB… But all to no avail.
When checking out the VCenter , nothing unusual!
But then when I went clueless, and just for the fun of it connected directly to the ESX Host instead of Vcenter, I saw a Snapshot task of the said VM running and hung at 95% for like 1 week already!!(from the backup exec VMWare backup)
So I cancelled this snapshot, but still not any luck with my D: Disk.
Then my collegue spotted something I didn’t see, for some reason we had 2 VSS providers:
-Backup Exec VSS Provider
As it turns out, when making backups of whole VMs, Backup exec generates an extra VSS Provider (BEVSS Provider) in the services console of windows, and when backups are complete removes it again. But because the snapshot hung, the service didn’t get removed and somehow backupexec messed up!
Now to solve this:
There is a script that get’s called after a VM Backup Job ( Post-Thawte-script.bat)
located in “c:\windows”
Run this script manually and reboot, this should fix the issue and remove the extra VSS Provider!!
more info here: http://www.symantec.com/connect/forums/backupexec-2010-bevss-provider-installs-inself