That problem is usually fixable on the server side by specifying save -c
{shortname} for the save command...  

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT listserv.temple DOT edu]
On Behalf Of Brian O'Neill
Sent: Friday, 28 April 2006 3:27 AM
To: NETWORKER AT listserv.temple DOT edu
Subject: Re: [Networker] Client backs up, but index has problems...

Problem seems to be solved. Unlike any of the other systems being backed
up, the system in question had the fully-qualified and old domain name
set with the "hostname" command. So it was the client itself that was
mucking it up.

All the savesets were under the old domain name, so the index wasn't
cross-checking properly.

I deleted and recreated the client under the old domain name, and it
seems happier for it.

They are a bit too paranoid with the system to change the hostname
locally... :(


Brian O'Neill wrote:
> This is a new one on me, as I once again inherit someone else's 
> Networker server...
> 
> I have a Networker 7.2.Build.172 server, backing up a Linux client
with 
> the 6.1.Build.186 client installed (I'll see about getting that 
> upgraded). The server seems to be talking to the client fine, and is 
> backing it up. The only warning is about the reverse DNS (something
else 
> to look in to), but its not affecting the backup itself.
> 
> The past few nights, its been complaining "No full backups of this
save 
> set were found in the media database" and proceeds to do a full
backup.
> 
> Yesterday I checked the Index for the GUI, although it was about 100% 
> utilized at over 2GB, no save sets volumes were listed. Also, the save

> sets were all marked "E" (recyclable), as if they expired right after 
> being completed.
> 
> Figuring a possible corrupted index, I ran nsrck -L6, and it wiped out

> the index completely, saying "no valid save times". That was fine with
me.
> 
> It ran again last night, and this time I expected the "No full
backups" 
> message...but the same problem existed. Running a nsrck -L2 didn't see

> any issues:
> 
> nsrck: checking index for 'foo.bar.com'
> nsrck: /nsr/index/foo.bar.com contains 170256 records occupying 25 MB
> nsrck: Completed checking 1 client(s)
> 
> But running an -L3 wiped it out again:
> nsrck: checking index for 'foo.bar.com'
> nsrck: WARNING: no valid save times for client 'foo.bar.com' - cross 
> check all (7) indexes
> nsrck: /nsr/index/foo.bar.com contains 0 records occupying 0 KB
> nsrck: Completed checking 1 client(s)
> 
> Any idea what is going on here? Why am I getting a corrupt index off
the 
> bat? Everything seems to be fine on the server...
> 
> -Brian
> 
> 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



NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Bank or third parties. If you are not the intended 
recipient of this email you should not read, print, re-transmit, store or act 
in reliance on this e-mail or any attachments, and should destroy all copies of 
them. Macquarie Bank does not guarantee the integrity of any emails or any 
attached files. The views or opinions expressed are the author's own and may 
not reflect the views or opinions of Macquarie Bank.

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