OKAY, I ran 'nsrck -L6' against the client. It completed reasonably fast
and showed no complaints, warnings or error messages. I then ran 'nsrls'
against the client and it reported the same info as before. BUT I guess
I don't see how a corrupt client index would affect database entries. I
mean, you should still be able to query savesets with mminfo regardless
of whether the client index has them or not, unless of course the volume
was recycled or the savesets explicitly removed, right? And, there's
nothing I can find anywhere to suggest that indexing is in anyway turned
off on this client anyway.
Next, I ran an mminfo command, including sscreate and sscomp. Very
interesting!!!
mminfo -s orion -q 'client=ldmspixie,sscreate>=10/20/04' -r
'volume,client,savetime(20),sscreate(20),name,sscomp(20)'
volume client date time ss created name
ss completed
FUL806 clientname 08/26/04 15:48:12 10/21/04 16:51:10 D:\
10/21/04 16:54:37
FUL806 clientname 08/25/04 17:58:10 10/20/04 19:30:36
SYSTEM DB:\
10/20/04 19:30:40
FUL806 clientname 08/26/04 15:42:37 10/21/04 16:46:18
SYSTEM DB:\
10/21/04 16:46:33
FUL806 clientname 08/25/04 17:58:09 10/20/04 19:01:48
SYSTEM FILES:\
10/20/04 19:03:07
FUL806 clientname 08/26/04 15:42:38 10/21/04 16:46:18
SYSTEM FILES:\
10/21/04 16:47:43
FUL806 clientname 08/25/04 17:57:50 10/20/04 19:01:43
SYSTEM STATE:\
10/20/04 19:02:01
FUL806 clientname 08/26/04 15:42:36 10/21/04 16:46:17
SYSTEM STATE:\
10/21/04 16:46:36
LTO156 clientname 08/25/04 17:58:15 10/20/04 19:01:46 C:\
10/20/04 19:02:41
LTO157 clientname 08/25/04 17:59:17 10/20/04 19:02:07 D:\
10/20/04 19:02:08
LTO162 clientname 08/26/04 15:42:39 10/21/04 16:46:31 C:\
10/21/04 16:47:17
LTO162 clientname 08/26/04 15:43:48 10/21/04 16:46:38 D:\
10/21/04 16:46:38
Something sure looks suspect here. Hard to believe a saveset could have
been created on the server with a date of 10/21/04 if the client
savetime was 08/26/04!!!! I haven't checked the clock on this guy yet,
but the Windows admin is looking into it.
George
Darren Dunham wrote:
>
> > If I run an mminfo command like: mminfo -s server -q
> > 'client=clientname,savetime>01/01/04', the last entries reported are
> > from Aug 2004, nothing later. Seems both saveset recover and the
> > database seem to think there's nothing after Aug. The browse policy on
> > the client is 2month and the retention policy is 1 year. Client is
> > running 6.1.1 and server is running 6.1.1 on Solaris 2.8. We have a
> > Linux storagenode running 6.1.1. Most clients, including this one, are
> > handled by the storagenode.
> >
> > I do not see this behavior on any of our other windows machines, and
> > this is the first time I have ever seen anything like this.
> >
> > Any ideas or suggestions?
>
> Could the client clock be off? Have you checked 'sscreate' instead of
> 'savetime'?
>
> --
> Darren Dunham ddunham AT taos DOT
> com
> Senior Technical Consultant TAOS http://www.taos.com/
> Got some Dr Pepper? San Francisco, CA bay area
> < This line left intentionally blank to confuse you. >
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|