Hi,

Could it have anything to do with this known issue?

Networker Solution ID# esg108377

Windows 2008 R2 64-bit backup failed

I have the same problem but my system is: Server Windows 2003 R2 standart edition and client Windows 7 32bit . My Networker is 7.6 build 142  . Please help me to solve this problem . Thanks

We have the same issue:

Server Win2003 SP2 32-bit - server NW 7.6.1.3 build 446

Client Win2008 SP2 64-bit - client NW 7.6.1.3 build 446.

savegrp: suppressed 2 lines of verbose output

System Writer - ERROR: Failed to save FileGroup files, writer = System Writer
System Writer - Error saving writer System Writer
System Writer - ERROR: Aborting backup of saveset VSS SYSTEM FILESET: because of the error with writer System Writer.
System Writer - Error saving
7162:save: save of VSS SYSTEM FILESET:\ to IP# failed
:  Failed with error(s)

In our case there is no file referenced so I'm not sure what NW's looking for.  I can't see what providing a drive letter for a disk that's offline will do for this but I could be missing something...  For these messages on a 2003 client we just used VSS:*=OFF and the legacy system states kicked in.  This won't be the case for 2008 right so we're reaching out before we go to EMC.

Cheers,

Carter

Hi,

I have the same issue with the aspnet_state.exe when the networker server tries to backup a Windows 7 64Bit client.

Networker server is running on RHEL 6 64Bit  and has the networker version 7.6 SP1 Patch 6 (7.6.1.6.Build.472)

Client is Windows 7 64 Bit SP1 and the networker client version is 7.6 SP1 Patch 6

Do you have any suggestions for me as I am on the latest release and also on the latest patch level ?

Regards

Georges Goebel

Yes – there were some code changes to address the VSS issue. Just be aware that 7.6.2 handles the back up of VMware differently. Be sure that you fully understand the difference (if you are using VMware) before you upgrade.

Mark Bellows

We just updated to 7.6.2 b631 - no more VSS issues.  We had to register / sign-up to gain restricted code releases.  I would recommend looking into this route.  We've got this version installed on about 90% of our clients - the NW server is still at 7.6.1.3 b446.

ciao,

Hello- Moving this over to the support forum to get additional help.

Thanks,

Allan

VSS can be a headache, that is for sure!!

Below are some Microsoft KB articles that may be useful.  Please read them and use them carefully!

Windows Server VSS issues:

Below are some articles that should be reviewed by a Windows server administrator. These articles pertain to VSS and possible issues that may occur.

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

Windows 2008 R2 64-bit backup failed

http://solutions.emc.com/emcsolutionview.asp?id=esg108377

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

Error message: "Not enough server storage is available to process this command"

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

Good luck!

Mark

you will need to update to a min of 7.6.1

no workaround will work good. Problem is how Networker is see it and handles it.  MS moved the shadow to the beginning of the OS from the end of the OS and Networker programmers are 2 year late in understanding and coding the change.

MS told the backup vendors this years before they did it and EMC did nothing as normal then they just wait until the customers call and write complaining, before they do anything.

You can also go to 7.6.2 if you want to be in the Beta yes now EMC is calling it RA but it is just a Beta to me... Beta comes out then it is release as a GA and EMC did not release it as a GA so it is still a Beta.

lee wrote: you will need to update to a min of 7.6.1 no workaround will work good. Problem is how Networker is see it and handles it.  MS moved the shadow to the beginning of the OS from the end of the OS and Networker programmers are 2 year late in understanding and coding the change. MS told the backup vendors this years before they did it and EMC did nothing as normal then they just wait until the customers call and write complaining, before they do anything. You can also go to 7.6.2 if you want to be in the Beta yes now EMC is calling it RA but it is just a Beta to me... Beta comes out then it is release as a GA and EMC did not release it as a GA so it is still a Beta.

It looks as if you have traveled in time.  For win2k8 you can use 7.5.2 and later code (where later is time depended and not release number depended as 2 code releases run in paralel).  The issue with VSS returning false paths on 64bit version is known MS issues and EMC included workaround for it on their side where with adjusted backup command ou can tell your application to ignore it.