VSS Error - Waiting for completion

Hello,

We have had an issue reported by Backup Exec 2012 SP4 with a snapshot initialization failure. We've gone straight to troubleshooting VSS Errors.

Please see output from vssadmin list writers:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {75125f49-fcec-4dd8-a554-5f0211499c6d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {2b1ccb69-85a1-4367-b3c3-0b4c9cc0bb0d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
   Writer Instance Id: {8e6de9da-48cd-43fb-b512-2ccf5db261fb}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {05bccc5c-8d2f-42f8-8c26-dcdc171d8c2f}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {379976b7-b90d-403c-808b-70e9d9614964}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {b88ead4c-8a17-40e2-a3f2-0fcb159d3179}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {a00d2612-7883-4411-9889-08ef6983a542}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {ee033332-b306-4215-93e2-5bc23ecfdf56}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {1b8c8171-4933-4db2-bbb5-1b8247095240}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {797d081d-06ac-408e-83dd-0c492daaafbe}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {ec02dfb5-95ed-4429-aaac-e9d8df5a096c}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {d0b799e6-80d3-4b34-9283-39976740a138}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {7455d0f2-57dc-4718-9eaa-59aa73a02f67}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {cee8c67c-b3ec-48be-9841-cc0c2f02470e}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {8582827d-520b-4653-bb61-254d20a05ac1}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WINS Jet Writer'
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {20649d01-22a1-410a-bcc1-9e8af0e1b243}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {88b3ffb9-9e4c-41fb-b534-9f8e7e755678}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {2823d506-b7e8-4268-ab4a-595e53e6d3db}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch4 VSS Writer'
   Writer Id: {35500004-0201-0000-0000-000000000000}
   Writer Instance Id: {14ce5ac3-8cb2-44e9-818d-758311fd209f}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {5722698d-0363-4252-a32b-074e8a0573d4}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {88306d19-9b23-4f91-b829-06868660ddef}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {347fb1c3-c99e-4699-b566-430b679cf55a}
   State: [5] Waiting for completion
   Last error: No error


There do not appear to be any errors within the output file. However, as soon as a backup is attempted of the System State using Backup Exec, the job fails immediately.

Any ideas?
utilizeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

perolinCommented:
First of all - reboot this server.

Then copy your backup-task that causes the problem and strip it down to small pieces to backup. Till you find the 'problem' are. Is it Exchange, SystemRessources, SQL, Advances Open File Option ...
0
Mohammed TahirMicrosoft Exchange and O365 AdministratorCommented:
As you posted the result of "vssadmin list writers" we found status of some writers are showing Waiting for completion,
Which means these writers are busy with some other process, so reboot your server once and check the status, now it should be Stable. Then try system state backup.


Tahir
0
utilizeAuthor Commented:
I discovered what the issue was, covered in these two articles:

http://www.symantec.com/business/support/index?page=content&id=TECH202992
http://support.microsoft.com/kb/2510009

We had the same issue at two different locations with identical USB drives.

The first instance had the USB job selected as the destination.

The second instance was a little more bizarre as the USB disk was attached to the media server but not include in the backup routine (source or destination). As soon as it was disconnected, the system state backups started working.

Bizarre.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
utilizeAuthor Commented:
The articles in the comment are what highlighted the issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.