It also sends you an annoying email every time, every backup cycle, every 
night.  Eventually, you will either just set up a filter to delete the blasted 
things (which actually report themselves - at least in my install that has been 
upgraded more times than Methusalah spent years on this planet! - as "client 
install" notifications!), or you'll browbeat the sysadmin for that client into 
at least creating an empty file of the same name to get NetWorker to STFU about 
the situation.  

sigh... sorry, but I feel better now.

 -Frank


On Jun 20, 2013, at 2:31 PM, Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV> 
wrote:

> Apparently a known issue, that can also show up when using 7.6.2, 
> according to Tech Support.
> 
> esg122495
> esg116035
> 
> Resolution
> Add the following command to the 'Backup command' attribute for the 
> corresponding client
> save -a '"ignore-all-missing-system-files=yes"'
> 
> That does work. It's a workaround, but it makes the backups work ...
> 
> 
> nsrd client notice: dctrtst007: VSS SYSTEM FILESET:\ ignoring missing file 
> [C:\windows\inf\oem5.inf] and continuing with saveset because client 
> attribute ignore-all-missing-system-files is set. 
> nsrd client notice: dctrtst007: VSS SYSTEM FILESET:\ ignoring missing file 
> [C:\windows\inf\oem10.inf] and continuing with saveset because client 
> attribute ignore-all-missing-system-files is set. 
> 
> Those apparently are what was causing the backups to fail. By ignoring 
> these non-existent files, the backup finishes.
> 
> 
> -- 
> Michael Leone
> Network Administrator, ISM
> Philadelphia Housing Authority
> 2500 Jackson St
> Philadelphia, PA 19145
> Tel:  215-684-4180
> Cell: 215-252-0143
> <mailto:michael.leone AT pha.phila DOT gov>
> 
> 
> EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on 
> 06/20/2013 11:37:19 AM:
> 
>> From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
>> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU, 
>> Date: 06/20/2013 11:37 AM
>> Subject: Re: [Networker] 8.0.1.5 client to NW 7.6.2 server - some 
>> work, some don't ...
>> Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
>> 
>>> And I was wrong, apparently (big surprise, eh?): 8.0.1.5 saveset ALL 
>>> worked without an error ...
>> 
>> Well, sorta ... Win2012 and Win2003 worked without problems, using 
> client 
>> 8.0.1.5 to NW server 7.6.2. 1 is a 64bit client, 1 is a 32bit client. 
> All 
>> worked as expected.
>> 
>> The 2 Win2008R2 clients did not. Same error as before:
>> 
>> * dctrtst007:DISASTER_RECOVERY:\ System Writer - ERROR: Failed to save 
>> FileGroup files, writer = System Writer
>> * dctrtst007:DISASTER_RECOVERY:\ System Writer - Error saving writer 
>> System Writer
>> * dctrtst007:DISASTER_RECOVERY:\ System Writer - ERROR: Aborting backup 
> of 
>> saveset VSS SYSTEM FILESET: because of the error with writer System 
>> Writer.
>> * dctrtst007:DISASTER_RECOVERY:\ System Writer - Error saving
>> * dctrtst007:DISASTER_RECOVERY:\ 90110:save: save of 'VSS SYSTEM 
>> FILESET:\' to server '<NW server>' failed: No such file or directory
>> * dctrtst007:DISASTER_RECOVERY:\ 90123:save: VSS save walkers: the 
> backup 
>> of save set 'VSS SYSTEM FILESET:\' failed.
>> 
>> So the backup fails, before it ever gets to any drives. If I bring up 
> the 
>> GUI to try a directed recover, I see only half the VSS entries I should 
>> see, no DISASTER_RECOVERY, and no drives. So that error makes the whole 
>> job fail, it doesn't just move onto the next element to be backed up.
>> 
>> VSSADMIN LIST WRITERS shows no errors, and all VSS WRITERS as stable. 
> The 
>> only thing the Windows event log shows is "backup failed". Networker log 
> 
>> (on client) shows nothing more than the above.
>> 
>> And, of course, all the storage nodes I wanted to upgrade this weekend 
> are 
>> all Win2008 R2 ... I guess that will be out.
>> 
>> I will try live Tech Support; maybe they can help ...