10-20-2014 10:00 AM
Hello, I am running BE 2012 and I'm trying to back up a new server. Since the server is offsite it is acting as it's own media server. When I try to back it up I am receiving:
- Snapshot Technology: Initialization failure on: "\\ServerName.DomainName.com\System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
I tried turning the AFO to software for the provider instead of Automatic. No Dice. The job is also throwing exceptions for every other component to the server in regards to VSS. When I check the event logs I receive 2 errors corresponding to one job:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({4a616c26-02a5-42f0-a4a0-f35e21f6925c}) [hr = 0x8000ffff]. Operation: Executing Asynchronous Operation Context: Current State: DoSnapshotSet
AND One saying the backup job failed... Can anyone give me some insight on how to fix this?
Solved! Go to Solution.
11-04-2014 09:18 AM
I think Maurijo has a good point... Why not try to reregister the vss writers via script... Obvisously I will back up all of my files before trying and then give it a go... If it works great, I saved myself a 4 hour round trip car ride and a long day... If not I am going to have to rebuild it anyway... I know it seems like a shortcut but honestly this is a very small server that really is only used for roaming profiles at the momment... Does anyone have a script to reregister the vss writers on a server 2008 r2 x64 box?
11-04-2014 11:26 PM
I used the one that is on the microsoft technote.
10-20-2014 10:11 AM
What state are the Writers in when you run vssadmin list writers on the affected server? If any are in error or failed a reboot should set them right again.
10-20-2014 10:33 AM
10-20-2014 10:35 AM
10-20-2014 10:43 AM
...some of your writers have failed, so a reboot should fix this as per lmosla.
However, if the OS of the server is Server 2003, you can download the latest VSS Rollup Patch and install this which should fix it. Alternatively try a repair of those VSS writers if Server 2003.
Thanks!
10-20-2014 11:03 AM
10-20-2014 11:10 AM
10-20-2014 12:59 PM
...then try a server reboot, and try disabling AOFO as well.
Thanks!
10-20-2014 06:40 PM
Search the Microsoft site and you would get the steps.
10-21-2014 05:34 AM
I will reboot the server tonight and let you know tomorrow. Thanks for the help!
10-22-2014 04:37 AM
Also check "vssadmin list providers" command, having more providers can give you problems as well.
10-22-2014 06:14 AM
>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
10-22-2014 06:42 AM
Rebooted and ran the job... same problem... disabled aofo and ran the job same problem... The same three writers failed
10-23-2014 05:58 AM
So here's something interesting if I restart the services that are associated with the VSS writers they are all stable with no errors:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {ca6cc659-27e8-472d-b171-7e641032f512}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {7bc35760-1bce-41a6-851b-b9da1f205479}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {18341640-ad57-42d2-92df-2c417a01703d}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {cf201752-d43f-4bca-ba78-a7e2971eaf07}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {8a70f6b2-2647-4a3f-898b-3e1529e18711}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {f729e510-6ee6-45d8-a033-45d5e29bf937}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {0ce63eae-4119-478f-8831-e8a254afdd7d}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {e2d38397-6f9f-409e-934c-2508df651bf9}
State: [1] Stable
Last error: No error
However whenever I try to run a backup job as simple as just the system state... I get this:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {ca6cc659-27e8-472d-b171-7e641032f512}
State: [7] Failed
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {83b7e90b-d7ee-4b41-86db-08ec1414c434}
State: [7] Failed
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {cf201752-d43f-4bca-ba78-a7e2971eaf07}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {d8b498d3-ee16-4475-b19b-b92f2dde7000}
State: [7] Failed
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {305e4550-626a-4b16-8323-6ec8000dc057}
State: [7] Failed
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {f729e510-6ee6-45d8-a033-45d5e29bf937}
State: [7] Failed
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {6ad4b9d0-5bed-4310-a68f-70ab9711ec89}
State: [7] Failed
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {e2d38397-6f9f-409e-934c-2508df651bf9}
State: [7] Failed
Last error: No error
Let me disclose I do not know that much about VSS... Is backup exec causing these writers to fail or is this an OS problem... How would I test it?
10-24-2014 12:10 AM
So you have one provider which is fine.
It is normal that they return to stable if you restart the services but it is highly recommended to reboot to clear the errors and return to stable state.
Yes, backup exec "causes" these writers to fail because backup exec asks for a snapshot but the real reason this fails is OS related and not backup exec.
The server you are trying to snapshot, is their enough free space on the C drive ?
Also for VSS error you have to go from the eventviewer and check the first errors that appear during the backup, these are the ones that will lead you to the solution.
Also is the server you are trying to backup virtual ?
10-31-2014 12:45 PM
11-03-2014 06:15 AM
Maybe to late but you don't have to rebuild the server te re register your vss writers. It can be done with a simple batch script and involves a reboot.
11-03-2014 07:37 AM
11-03-2014 08:28 AM
Please be careful when doing any VSS registration steps with Windows 2008 or newer.
Microsoft have released information stating it can break your server to the point where you could have to re-install the operating system. Please see Microsoft KB http://support.microsoft.com/kb/940184
Important This article is not for use with Windows Vista, with Windows Server 2008, or with later Windows operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest-based. Trying to manually register specific components, as described in the following steps, can have unexpected results that may require you to reinstall Windows to resolve.
-----------
For generic information on troubleshooting VSS issues with Backup Exec please review
http://www.symantec.com/business/support/index?page=content&id=TECH173983
11-04-2014 12:01 AM
That is correct, but he was intending to rebuild it anyway so he can give it a shot I guess?
And to be honest, I done it over 50 times on server 2008 R2, never had any issues.