In regard to: Re: [Networker] How to refresh client information, Davina...:

I don't think this ever gets updated. It is set when you first create the client. I have tried in the past to update this using nsradmin but it refuses to do it - I think it is read-only data. Raise a bug with EMC if you feel strongly about it.

Now I've seen everything.  Davina was wrong about something
Networker-related!  ;-)

Am I?  :-(

I have just had a look at a 7.2.1 Solaris server, and many of the
clients have no information whatsoever about the NetWorker version, OS
type etc. Am I missing something here?

I'm not sure why you have clients that aren't filling in the "client OS
type", "NetWorker version", etc, but ours always have.  The only time
we see a client with no information in those fields is when it's
new and hasn't yet been backed up.  Right now, all 116 of our clients
have both OS and client version filled in and current.

I don't think I knew about these "hidden" fields back in the NetWorker
4.x days, but even back in the NetWorker 5.x days, ours were filled in
and kept updated.  I used to rely on those fields to track what versions
our clients were running, before you shared how to get the information
directly from the client.

I just did a test with a client that I found that we had that didn't
have the 7.2.2 client software on it:

$nsr_osver_list | egrep bb-web1
bb-web1-s.ndsu.nodak.edu            Linux                 7.1.3.Build.421
$sudo savegrp -p -c bb-web1-s.ndsu.nodak.edu 'Testing'
[output elided]
$nsr_osver_list | egrep bb-web1
bb-web1-s.ndsu.nodak.edu            Linux                 7.1.3.Build.421


That means that a successful probe isn't enough to get the info updated.
However, if I remove the '-p' from the savegrp arguments and run it again,
so it's a real backup, and then run the nsr_osver_list script in a
different window while the backup is still in progress, I can see that
the info has updated:

$nsr_osver_list | egrep 'bb-web1'
bb-web1-s.ndsu.nodak.edu            Linux                 7.2.2.Build.422



So, a probe won't do it but a backup that can successfully connect to
the client will, even before the backup finishes.

I know I can query these by
connecting to the client (echo p | nsradmin -p 390113 -s clientname) but
how do I get the server to update?

That echo trick is a great one, which I first learned about in a post
you made here long ago.  Here's the wrapper script I use for it:

#! /bin/sh

#
# Author: Davina Treiber et. al.
#
# Synopsis: Given a client name on the command line, contact that client
# and ask it for info.
#

if test $# -lt 1 ; then
        echo "$0: usage: nsr_get_client_version_from_client clientname" >&2
        exit 1
fi

printf "%s\n%s\n" 'show NetWorker version:' 'print type:NSRLA' \
        | nsradmin -p390113 -i - -s "$1" \
        | sed -e 's/^ *NetWorker version: //' -e 's/;//g'



Tim
--
Tim Mooney                                           Tim.Mooney AT ndsu DOT edu
Information Technology Services                      (701) 231-1076 (Voice)
Room 242-J6, IACC Building                           (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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 with 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