In regard to: [Networker] media db began associating a client's savesets...:

We have a problem with our media database:

mminfo reports that savesets for a particular client began to be associated
with the server's name and clientid some time ago. nsradmin reports that
both the client and the server's clientids are distinct and have not
changed. Nothing notable was observed in the logs around the time that
association changed nor was a significant change in incremental-saveset-size
observed.

Running scanner -iv -S ssid device produces the message: "client is renamed
from the_client_name to the_server_name"

What could have caused the association to change?

Check to see if either of these (especially the client) have any aliases
listed in the client definition.  Verify that the server resolves (DNS,
NIS, /etc/hosts, or whatever combination of that and other "hosts" entries
you have in your /etc/nsswitch.conf) the client name and any aliases and
that those names and aliases all resolve to the client.

What must be done to cause new savesets to be properly associated with the
client?

Track down what's causing your problem, and fix it.  ;-)

What can be done to reassociate existing savesets in the media database with
the client's clientid?

I'm not sure that's going to be possible.

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak 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

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=