hi,

i´m just showing for my own problems in this list,and now i see your problems,

the other person,which wrotes you, tells about saving in the evening,thats a
bad controlled solution,because he doesn´t know why it´s fact,why this will
works.

we have this problem sometimes in our big environment,and i can tell
you,it´s a internal legato-problem,

i think you are very sure,that your clients have truely the right aliases
and names in the client-resource.sure.
but control if the names are exactly that what´s in your client-host-file.
you can check with savegrp -pvvv -l full -c <clientname> <group>
too if there are any other problems maybe before this message occurs,that
can be!!!!
if this is not true,than do a clientsave for example:

save -e week -s <server> -b <pool> -N /etc/hosts /etc/hosts

if this will work,you should test now a backupserver saving.

if the problem still exist,you do a

savegrp -O <NWSERVERGROUP>

you have to use for NWSERVERGROUP the group in which is the backupserver.

this command will do a bootstrap for all the clients,and that´s why the
other person tolds you why the backup runs in the evening,hey surely makes
some backupserver backups on the day,and there is a bootstrap-saving at
last, too.

if this all doesn´t work,use the nsrim -X to control the MDB.

i think legato has in very strange times and action some problem to write
into his resources.and then the backupserver doesnt know that the client is
existing.

at least is nslookup <client>
and nslookup <IP> given the right names and IP??


nice greetings,dennis

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=