Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

V-79-10000-11226 - VSS Snapshot error - How to prevent it?

Created: 01 Feb 2013 • Updated: 08 Apr 2013 | 5 comments
This issue has been solved. See solution.

I'm running Backup Exec 2010 and we will occasionally have a backup fail on a machine (not always the same one) with the error message:

V-79-10000-11226 - VSS Snapshot error

(I can provide the full text of the error message if needed)

After some research, I found this article on Symantec's web site:

http://www.symantec.com/business/support/index?page=content&id=TECH77585

That fixes the problem and backups run on whatever machine had the problem, but that leaves two big questions:

1) Is there a way to test for this problem without having to actually run the backup?

2) Is there a way to prevent this problem from popping up at all?

This seems to come up rather frequently for us and it's pretty random, which is making it very hard to track down, so any help would be greatly appreciated.

Thanks!

Bryan

 

Comments 5 CommentsJump to latest comment

santoshpawar's picture

Hi,

If you provide the full text of the error message then it will be easier to find the solution.

Regards,

Satnosh Pawar.

 

Bryan Francoeur's picture

Hi Santosh:

Below is the full text of the error message.  I'm going to bring up the solutiions that you and Craig discussed below and see if we can implement them.

Best regards,

Bryan Francoeur

            Server - VONDC2.burlington.vtoxford.org
 - AOFO: Initialization failure on: "\\VONDC2.burlington.vtoxford.org\C:". 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.
Network control connection is established between 10.0.40.223:59939 <--> 10.0.40.3:10000
Network data connection is established between    10.0.40.223:59945 <--> 10.0.40.3:10001
Set Information - \\VONDC2.burlington.vtoxford.org\C:
                        Backup Set Information
Family Name: "Media created 1/28/2013 10:00:01 PM"
Backup of "\\VONDC2.burlington.vtoxford.org\C:"
Backup set #13 on storage media #1
Backup set description: "Daily Differential Backup"
Backup Method: Differential - Changed Files

Backup started on 1/29/2013 at 3:28:49 AM.
Backup completed on 1/29/2013 at 3:28:57 AM.
Backup Set Summary
Backed up 13 files in 146 directories.
Processed 44,291,933 bytes in  8 seconds.
Throughput rate: 317 MB/min
Compression Type: Hardware

 - AOFO: Initialization failure on: "\\VONDC2.burlington.vtoxford.org\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.
The following volumes are dependent on resource: "C:" "\\?\VOLUME{5B3CBBE2-6373-11DF-908D-806E6F6E6963}" .
 

CraigV's picture

Hi Bryan,

 

1. there is no way to test whether or not the VSS provider will fail. You can try scheduling a test run, but not sure this will even work. This is unfortunately something that happens when VSS is called by the backup.

2. Not really...make sure that your VSS provider is set to Automatic in the job setup and see if this fixes the issue.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

santoshpawar's picture

Hi Bryan,

Or make below changes and verify......

In the job Properties, Under Settings, in Advanced open file option make the following changes :-

A)  Set Open file Configuration to Microsoft Volume Shadow Copy Service (Windows 2003 and later).
B)  Select the Snapshot provider as System - Use Microsoft Software Shadow Copy Service Provider.

 

Then Run the job.

 

Thanks.

SOLUTION
Gurvinder Rait's picture

did you ever had BESR running on the servers where the above problem is seen ? The reason I want to know this is that everytime you would not have to delete those GUIDs. Is the document really helping you resolve the Issue or just a simple reboot of the server fixes the Issue.

You can schedule a script to run vssadmin list writers command and keep appending to the same output file. If you run into the error check the output file to see if any writer had become unstable or was in failed state. If that is the case next time would know if any writers failed , you can reboot the server and then let the backup run. 

The above would involve manual work.