Jump to content


Photo

Frequent Failed Backups - VSS Issues - 2008 R2 Server

VSS Failed vssadmin

  • Please log in to reply
2 replies to this topic

#1 Matt Rotroff

Matt Rotroff
  • Members
  • 1 posts

Posted 13 September 2017 - 08:23 AM

Hi Everyone,

 

We have been seeing an increased amount of failed backups on our Telnet Server. In the past, maybe once a month or so I would get an email notification alerting me of a failed backup.

 

Now, I might get an email twice a week letting me know that the backup has failed; this has been happening for about 3 weeks. For months, I have regularly restarted our Servers on Sundays.

 

I looked at the BBTrace.txt file and found the errors listed below in the log. If I open up a command prompt and run the "vssadmin list writers" command I do see that some of our writers are in a failed state. See below for writer status. Someone from Barracuda recommended going into "services" and restarting the "COM+ Event System" and Volume Shadow Copy Service. After restarting both services, the writers do appear to be in a STABLE state.

 

Yesterday, I restarted the services and the writers were all in a stable state, yet the evening backup failed. We have not made any configuration changes to our server. We are running: Barracuda Backup Agent 6.3.04-200513-rel

On a Windows 2008 R2 Server

 

I am going to follow up with Barracuda but wanted to post to see if anyone had any recommendations?

 

BBTrace.Txt

 

09/08/2017 22:32:39 0x00009040 YJobManager: Processed job_create for 'listing' job with jobId: 'j44' from an internal request.
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : CheckWriterStatus from 'YVssManager::DoSnapshotSet'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [System Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [ASR Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [WMI Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [Shadow Copy Optimization Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [Registry Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [IIS Config Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [COM+ REGDB Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/08/2017 22:33:12 0x0000cb20 YVssManager j43: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Backup Components Document:


09/12/2017 22:31:08 0x00006e00 YVssManager j25: YJobBackup::m_vssMgr: Required service 'swprv (Microsoft Software Shadow Copy Provider)', is not running.
09/12/2017 22:32:15 0x00006e00 YVssManager j25: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : CheckWriterStatus from 'YVssManager::DoSnapshotSet'
09/12/2017 22:32:15 0x00006e00 YVssManager j25: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [COM+ REGDB Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/12/2017 22:32:15 0x00006e00 YVssManager j25: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [Shadow Copy Optimization Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/12/2017 22:32:15 0x00006e00 YVssManager j25: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [ASR Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/12/2017 22:32:15 0x00006e00 YVssManager j25: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Bad writer status [Registry Writer]: 'VSS_WS_FAILED_AT_FREEZE'
09/12/2017 22:32:15 0x00006e00 YVssManager j25: YJobBackup::m_vssMgr: YVssManager::CheckWriterStatus : Backup Components Document:

 

VSSAdmin_ListWriters

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
© 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

C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative comman
© 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: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {749db891-affc-422b-a86f-a9e8ec3b804e}
   State: [9] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {707fbe5a-27c6-40b2-b7bd-399834f29dbe}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {ab787c8d-9d10-4abb-b879-22ebdc640c34}
   State: [9] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a06e28a8-d373-4495-88f1-6261f8a6907d}
   State: [9] Failed
   Last error: Timed out

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {59b1d85f-8747-454f-8f0c-1a50b9bebfc6}
   State: [1] Stable
   Last error: No error



#2 David Waller

David Waller
  • Members
  • 163 posts

Posted 13 September 2017 - 04:04 PM

We experience this same problem with our vCenter server, AntiVirus Server, and an application server.  A mixture of Physical and Virtual machines.  I get the error message that it failed and then I restart the appropriate services on the box for the VSS writer that shows failed.  The backup will run fine for a few days and then fail again.  We're on Firmware 6.4.02.



#3 David Waller

David Waller
  • Members
  • 163 posts

Posted 13 September 2017 - 04:05 PM

We experience this same problem with our vCenter server, AntiVirus Server, and an application server.  A mixture of Physical and Virtual machines.  I get the error message that it failed and then I restart the appropriate services on the box for the VSS writer that shows failed.  The backup will run fine for a few days and then fail again.  We're on Firmware 6.4.02.

Just to add a little more information, all 3 servers are also Windows Server 2008 R2.