Make sure that the permissions on the folder are set to allow the backup
user (sometimes it's not LOCAL SYSTEM) access to the files and
directories there.

We had a group that was convinced their data could not be allowed to be
read by anyone outside of their group, and unfortunately, that included
the backup account.  They were disappointed when the backup account
couldn't restore their files.  (both because they hadn't been backed up,
but also because we wouldn't have been able to write the files there
anyway)

The frustrating thing was that there was no "Permission Denied" in the
backup logs, just a silent failure.

--Joe 

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Lusby, James
> Sent: Wednesday, July 05, 2006 2:20 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Missing data from server backup
> 
> I checked for that earlier and there is no rule causing any 
> directories
> or files to be skipped...
> 
> -----Original Message-----
> From: Stan Horwitz [mailto:stan AT temple DOT edu] 
> Sent: Wednesday, July 05, 2006 2:19 PM
> To: Lusby, James
> Cc: Legato NetWorker discussion
> Subject: Re: [Networker] Missing data from server backup
> 
> 
> On Jul 5, 2006, at 2:14 PM - 7/5/06, Lusby, James wrote:
> 
> > After reading your previous email I went through and 
> checked to see if
> > any of the missing paths (and this time I checked the entire path  
> > name)
> > matched that 255 limit, and even with the file name it did not  
> > exceed 40
> > characters so we are well below the 255 limit.
> 
> Verify that no client or server based directives are causing those  
> files (or folders) to be skipped.
> **********************************************************************
> This e-mail and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to 
> whom they are
> addressed. The views, opinions, and information expressed in 
> this message
> represents those of the individual sender and do not reflect 
> the views of
> Ruesch International, Inc. Take notice that the employees 
> and/or agents of
> Ruesch International are not authorized to make corporate 
> commitments or
> representations via e-mail and no statement or representation 
> made in this
> e-mail is binding upon Ruesch International. Ruesch cannot 
> guarantee the
> integrity or the confidentiality of any incoming or outgoing e-mail
> communication.
> **********************************************************************
> 
> To sign off this list, send email to 
> listserv AT listserv.temple DOT edu and type "signoff networker" in the
> body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems
> wit this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER