06-20-2014 06:26 AM
Hi
We were backing exchange and system state ok till around 2 weeks ago.
It started failing with error
Backup- OPTICSBS2008 - AOFO: Initialization failure on: "\\OPTICSBS2008\Microsoft Information Store\First Storage Group". 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.
- AOFO: Initialization failure on: "\\OPTICSBS2008\Microsoft Information Store\Second Storage Group". 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.
- 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.
Event viewer error id comes up as id 12293 vss error.
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({130b2079-8c20-48fc-bf39-00b0a249de9a}) [hr = 0x8000ffff].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
I followed different links on the forums and server does not have other vss providers than microsoft system provider below output of vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
I have reregisterd vss writers but that did not help, tried to run it with AOFO set to automatic and to use Microsoft system provider, tried to do that withot AOFO option, but still same issue.
Have uninstalled BE and installed it back still the same issue.
Any help would be appreciated.
Solved! Go to Solution.
06-20-2014 12:20 PM
Hello lukaszm,
Is this a Windows 2008 server? If so refer to this document http://www.symantec.com/docs/TECH154496
copied directly from the referenced link:
'Right-click any local disk.
Select Configure Shadow Copies.
Highlight Volume with Volume name reporting the Exception in the Backup Job Log
Click on Settings.
Set the Maximum Size to No Limit.
NOTE: If No Limit is already selected click Use Limit and accept the default size. Click OK then OK. Then go back in and set the Maximum Size to No Limit and click OK. OK.
Attempt the Backup Job'
Hope this helps
06-20-2014 06:58 AM
...have you restarted the server? Might also be worthwhile to do the following:
* Open a command prompt and type: vssadmin list writers
* Check for any writers that are not stable and running. If in error, and a restart doesn't fix it, you might have to check on Microsoft for a resolution.
Thanks!
06-20-2014 12:20 PM
Hello lukaszm,
Is this a Windows 2008 server? If so refer to this document http://www.symantec.com/docs/TECH154496
copied directly from the referenced link:
'Right-click any local disk.
Select Configure Shadow Copies.
Highlight Volume with Volume name reporting the Exception in the Backup Job Log
Click on Settings.
Set the Maximum Size to No Limit.
NOTE: If No Limit is already selected click Use Limit and accept the default size. Click OK then OK. Then go back in and set the Maximum Size to No Limit and click OK. OK.
Attempt the Backup Job'
Hope this helps
06-20-2014 02:37 PM
06-20-2014 03:08 PM
glad it helped,
you can set a limit for the snapshots by following the steps here: http://www.symantec.com/docs/TECH83223
Me being dumm here i had simmilar issue earlier and your solution resolved the issue, this time i did not came accross this one and did not try it.