Ah! If the client has had its domain changed then try removing the client
package... And the /nsr directories and reinstall....
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT listserv.temple DOT edu]
On Behalf Of Brian O'Neill
Sent: Tuesday, 25 April 2006 11:34 PM
To: NETWORKER AT listserv.temple DOT edu
Subject: Re: [Networker] AW: [Networker] Client backs up, but index has
problems...
I _soooo_ want to wipe this thing out and start again... :)
Going on the name resolution, here is what I've got:
The "reverse DNS" warning was about a virtual address on the server, not the
client.
The clients reverse DNS comes back as a different domain. That is, the client
is configured in Networker as "foo.bar.com", but the reverse resolution comes
back as "foo.quux.net". The reverse name _is_ configured as an alias for the
client.
mminfo shows that the savesets are being saved under the reverse name, but
specifying either the configured or reverse name does show them to me.
Is this the crux of the problem? I would think I'd see it on other hosts as
well...there has been a partial domain change here that they are still working
on.
Grohal, Klaus wrote:
> Brian,
>
> I don't believe that your index is corrupt, I think your issue is a name
> resoltution of the client.
>
>
> regards
>
> Klaus Grohal
>
>
> -----Ursprüngliche Nachricht-----
> Von: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] Im Auftrag von Brian O'Neill
> Gesendet: Dienstag, 25. April 2006 14:47
> An: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Betreff: Re: [Networker] Client backs up, but index has problems...
>
> A bit more info on the below problem...
>
> Looking at previous backups (again, I'm just inheriting these problems
> now... :( ), it seems it has ALWAYS been doing a full - I don't see
> any incrementals, so this client has always been "corrupt".
>
> Also, the "expired" issue was only the one time - the rest list as
> "browsable", even though there is no index for them...
>
> Lastly, the Networker server is running Solaris 9 with UFS filesystems. >
> There is a client with a 3GB index and it seems fine.
>
> 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
>
> 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
|
