Solved

Vss writers failed and timed out with symantec backup exec and cloud based

Posted on 2013-01-10
4
1,857 Views
Last Modified: 2013-01-30
My backups are failing, and when running vssadmin, it shows most of my writers are in a failed state.  I rebooted the server and they are still appearing.  I have two backup solutions, backup exec 12.5, and a cloud based backup.  originally it was an issue with conflict times, however these have been changed so jobs don't run on top of each other, but I still have this issue.  the results of vssadmin:

C:\Users\Admin>vssadmin list writers
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: {bae4b67c-c363-42b5-9431-4eae694091d3}
   State: [9] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {0f317534-3ac4-40c9-b1c7-994fbe0d7723}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {3524e278-e157-4f09-a425-dc15875db147}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {71709074-d481-4866-bfed-1b4e2370dfe1}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {350fabc4-02a1-401c-a173-783232c236ee}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {2b7d61f2-efb9-4e4c-b765-d8d13f8f85f1}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c3aeedd7-863a-4a3c-9066-1853224fdf88}
   State: [1] Stable
   Last error: No error

Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {981f1704-d8eb-4745-aa39-2149c8f0a1f9}
   State: [9] Failed
   Last error: Timed out

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {a5fbe841-33d3-4daa-827a-bd595d521a3b}
   State: [9] Failed
   Last error: Timed out

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {7513fd0f-a836-4a0a-97ea-bff584777e48}
   State: [9] Failed
   Last error: Timed out

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {103b01b6-031c-4407-9883-bd3bc0d8e117}
   State: [9] Failed
   Last error: Timed out

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {a178e048-643e-4166-9116-b20b29c9d9f5}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {cf8d6c59-5151-455e-8fa1-7410f2ea10b4}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {f4e2e785-73b7-42ab-b2cd-3162c7e4ce0c}
   State: [9] Failed
   Last error: Timed out


C:\Users\Admin>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'CA XOsoft VSS Provider'
   Provider type: Software
   Provider Id: {564f2dcc-1817-4292-b4fc-0988b29fc840}
   Version: 1.0

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Not sure what else to do at this point.

Thank you.
0
Comment
Question by:fireguy1125
  • 3
4 Comments
 
LVL 1

Author Comment

by:fireguy1125
ID: 38762855
This is on a Windows Server 2008 Standard with Service Pack 2 - Backing up Data files.
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38765937
Just check this once

http://support.microsoft.com/kb/2009272
http://support.microsoft.com/kb/955078

Can you also check events in the App logs when the backup fails so we will have a broader view of the issue

- Rancy
0
 
LVL 1

Accepted Solution

by:
fireguy1125 earned 0 total points
ID: 38819262
The issue was actually indeed a cloud based backup job that was still running at that time. When this was rescheduled the errors stopped. Thanks.
0
 
LVL 1

Author Closing Comment

by:fireguy1125
ID: 38834525
Found own solution
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

OfficeMate Freezes on login or does not load after login credentials are input.
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question