Windows 2008 R2 VSS Error

Question

I have the same error occur on two servers throwing up VSS errors: The servers are Windows 2008 R2 Legato 7.5 sp3 client The error message is the same on both servers (I've omitted some of the verbose details for clarity) 113 MB VSS SYSTEM BOOT:VSS Writer:ASR Writer is not supported, ignoring it. System Writer - ERROR: Aborting backup of saveset VSS SYSTEM FILESET:because the error with the writer System Writer 7162:save: save of VSS SYSTEM FILESET :\ to failed. One one of the servers I have the following additional error message : Windows Internal Database - ERROR: Faild to save FileGroup files, writer=SQLServerWriter Windows Internal Database - ERROR: Aborting backup of saveset VSS SYSTEM SERVICES: because of the error with writer Windows Internal Database. Windows Internal Database - Error saving 7162:save: save of VSS SYSTEM FILESET :\ to failed. Has anybody else experienced this error? I know that the version of Legato I mentioned is supposed to support 2008R2 but is there any else that I need to do from the client end? Any help would be appreciated.

Panwar · Answer

Hi Please run the vssadmin list writers on the both clients and check the status of the writers.Status of the writers should be stabe and has no errors. Thanks & Regards Panwar

stonedragon2k · Answer

Thanks Panwar. I'll do that and let you know what I find. r, Ken

ble1 · Answer

Those details removed might be the key.  I remember in the past with Windows internal database there has been an issue with path using double slash which would cause this error.  Workaround was to deattach database, correct path and attach it back.  You will also find this mentioned somewhere on forum and I believe article in KB exists too.  Might not be your case, but worth checking out.

Mark_Bellows · Answer

There are several known issues with VSS on Windows servers - both 2003 and 2008. Below is a list of the Microsoft KB areticles that apply to both 2003 and 2008 servers. Review them and see if anything might help you with your situation.

Knowledge base articles - known Windows 2003 VSS issues:

A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003 - Last Review: July 2, 2010

http://support.microsoft.com/kb/833167

Exchange VSS backup fails on an Exchange Server 2003 server - February 20, 2010

http://support.microsoft.com/kb/924262

Various issues may occur on a Windows Server 2003-based computer that is running the Volume Shadow Copy Service - April 27, 2010 - April 27, 2010

http://support.microsoft.com/kb/940032

Exchange Server 2003 data backup and Volume Shadow Copy services

http://support.microsoft.com/kb/822896

Knowledge base articles - known Windows 2008 VSS issues:

VSS snapshot creation may fail after a LUN resynchronization on a computer that is running Windows 7 or Windows Server 2008 R2 - November 25, 2009

http://support.microsoft.com/kb/976099

Backup fails with VSS Event ID 12292 and 11 on Windows Server 2008 and Windows Server 2008 R2 - January 20, 2010

http://support.microsoft.com/kb/2009513

No VSS writers are listed when you run the “vssadmin list writers” command in Windows Server 2008 R2

http://support.microsoft.com/kb/2009550

http://support.microsoft.com/kb/2009533

General VSS articles to review:

The backup process may fail and a time-out error may occur in Volume Shadow Copy Service writers

http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/77862/VSS-Writer-errors-during-backup

Event ID 9840 or 9607 is logged when a VSS backup operation fails in Exchange 2007 or in Exchange 2003

http://support.microsoft.com/kb/930800

Best Practices for Using Volume Shadow Copy Service with Exchange Server 2003

http://technet.microsoft.com/en-us/library/aa996004(EXCHG.65).aspx

NetWorker

Was this post helpful?