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

VSS timeout issues, restart not suitable solution

Created: 12 Sep 2013 • Updated: 26 Nov 2013 | 9 comments
This issue has been solved. See solution.

Hello

I have had continual issues with vss writers time outs on one of our machines we are backing up.

Running Windows Server 2008R2 SP1, using BE2010 R3 SP1

The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job.

The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points.

I have selected "Process logical volumes for backup one at a time" too see if this helps.

Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues.

Thanks for the help

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: {bcedc94e-0c21-4212-8bbf-b65083123138}
   State: [9] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e}
   State: [9] Failed
   Last error: Timed out

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177}
   State: [9] Failed
   Last error: Timed out

Operating Systems:

Comments 9 CommentsJump to latest comment

Giermo's picture

thanks, but i already read that one, and it was of little help. Glad i read it though, as it says that registering the dll's is a bad idea on 2008 server

ANevatia's picture

Hello,

Please get in touch with Symantec Support to further diagnose the issue.

Thanks,

ANevatia

Giermo's picture

I have attempted. They said on multiple occasions to talk to MS, as its their issue.

Kunal.Mudliyar's picture

Hi there.

Symantec does not have any "system writers by symantec" , we reply on Microsoft OS writers for the backup.

Symantec can not do much if the Sytem writer is failing something which only MS can help you with.

Just to isolate though can you reboot the server so the writer is stable on the server and later try a system state backup of the server in question using the WBadmin command line utility and see if the writers fail or not.

Thanks

Technical Support

Symantec

Vishal Shinde's picture

Hello Giermo,

Greetings!

I am pretty sure we (Symantec and you) both share a common honest intention of resolving this issue at its earliest.

Now few technical facts to note, that the issue is caused due to timeout problem with VSS writers.

Additionally, I find that IIS Config Writer and WMI Writers have similar problem.

These Writers (System writer, IIS Config Writer and WMI Writers) are integral part of operating system, a Microsoft proprietary and is responsible for multiple OS activities, apart from Backup /restore.

Now seeking help from Symantec support to fix the OS issues, (Whose expertise is not questionable, but confined to BE Application) will be like hiring a carpenter and not cobbler to make your shoes.

We need to seek thoughts from OS expertise to reduce the risk of landing into bigger OS troubles.

This is probably the reason why you are directed to Microsoft support.

Kind regards,

S

Vishal Shinde

Sr.Learning Consultant

Symantec Education Services

SOLUTION
Vishal Shinde's picture

Hello Giermo!

Greetings!

I was keen to know if there was any progress on this problem?

Regards,

S

Vishal Shinde

Sr.Learning Consultant

Symantec Education Services

pkh's picture

If you want an update on the problem, send a PM to the user