Hmm - another option is that it has a backup command which includes save -S, 
which will purely allow saveset recovery and not build the index.
 
Is all for this one :)
 
Cheers,
 
Stuart.

________________________________

From: Legato NetWorker discussion on behalf of Stan Horwitz
Sent: Tue 25-Jul-06 02:50
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] client is not getting index entries written...



On Jul 24, 2006, at 7:29 PM, Brian O'Neill wrote:

> Added info:
>
> If I run a manual "save" from the client, and I specify the 
> client's name with the "-c" option, the data winds up in the index 
> (and it seems to even back-populate the other filesystems as well, 
> if that's even possible). However, the default save command run 
> from savegrp, which doesn't use the "-c", results in no index data 
> being stored.
>
> Why isn't "save" getting the proper name? "hostname" returns the 
> short name of the host. I've tried adding the client with both 
> short and long name, and it doesn't seem to matter.

I have seen that kind of behavior happen with multi-homed clients and 
also with a DNS error. Check both.

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