12-20-2010 01:03 PM
Hi,
We have a problem with BE 2010 r2, where everything seems to be backing up fine apart from the BE server itself.
The issue is VSS related. The backup gets to about 19GB and then fails...
Here are some errors:
-------------------------------------------------------------------------------------------------
Job ended: Tuesday, 21 December 2010 at 2:02:01 a.m.
Completed status: Failed
Final error: 0x8004230f - 0x8004230f (2147754767)
Final error category: Other Errors
For additional information regarding this error refer to link V-79-32772-8975
-------------------------------------------------------------------------------------------------
Click an error below to locate it in the job log
Backup - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
-------------------------------------------------------------------------------------------------
Best Regards
MJ
12-20-2010 01:14 PM
Hello
Have you checked the below article.
http://www.symantec.com/docs/TECH65148
12-20-2010 01:20 PM
Hi,
Please make the changes as per the following link, select the correct option in AOFO & re-try the job for system state to check :
12-20-2010 01:50 PM
Thanks for trying:)
Regards
MJ
12-20-2010 02:20 PM
Thanks for trying to help...
MJ
01-06-2011 08:15 AM
I am having the same issue. V-79-10000-11226 - VSS snapshot error. The microsoft Volume Shadow copy service (VSS) snapshot provider selected returned: "unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
Any other input from Syamtec on this one??
01-12-2011 08:01 AM
I could have suggested better if i knew the environment completely .So am including some of the articles that can help you identify and fix the problem.
Please check the following :
"vssadmin list providers"
check if any writer has issues.(if required try the same after a reboot)
"vssadmin list providers" (Make sure you dont have multiple providers)
If the job uses AOFO try selecting the Microsoft vss provider from the list.
Microsoft Windows 2008 R2
Try to assign drive letter to System reserved partition.
http://www.symantec.com/docs/TECH140909
Thanks
Jay
01-12-2011 01:26 PM
Yes Finally heard from Symantec on this. Apparently this is an issue with the Microsoft writer, and has to be rectified with Microsoft.
MS know of this issue and have a fix for it, however it has to be requested directly from them.
Best bet is to do what Jay suggested below, and get back to MS with the issue of writer, then request a patch. This is the process I will start today.
Best Regards
MJ
01-12-2011 01:28 PM
This has all been tried already... issues lies within the ms writer..
please reffer to comment above.
Thanks for your kind input.
MJ
01-13-2011 07:59 AM
If you are backing up Exchange 2007 it also is a known issue for their VSS Writers. The fix is to update your Exchange server to SP3.