duh!

yes I did of course mean to write 'save -c' instead of 'save -s'. sorry
about that.

As for the whole hostname based authentication discussion, yes it really
is time legato moved forward into the 1990's and did something based on
either kerberos or perhaps a more interesting approach would be to use a
CA to issue client certificates - of course the biggest problem with
this is that the client's private keys would be backed up on tape along
with everything else.

-----Original Message-----
From: Tim Mooney [mailto:mooney AT dogbert.cc.ndsu.nodak DOT edu]
Sent: Tuesday, 23 August 2005 2:30 AM
To: Legato NetWorker discussion; Peter Viertel
Subject: Re: [Networker] 7.1.3 client DNS checks and multihomed clients


In regard to: Re: [Networker] 7.1.3 client DNS checks and multihomed...:

> When I was moving clients to 7.1.2 I had a problem with the same error
> message and stumbled upon a solution in the networker knowledgebase,
> which is probably quite an achievement in itself.

:-)  You're correct, it is.

> Normally in your client records you leave the 'Backup command:'
property
> blank, however if your client record's main name is called
> imap1.fred.edu then put in 'save -s imap1.fred.edu'.

This is very good information!  If I could get it to work, it would
provide us with at least a temporary workaround for the problem, while
I talk with Legato about the issue.

I haven't been able to make it work for any of our clients, though, so
I must be doing something wrong.  As an example, we have clients created
within NetWorker named `netreg-2.ndsu.nodak.edu' and
`netreg-2.ndscs.nodak.edu'.  The hostname command on those boxes returns
`netreg.ndsu.NoDak.edu' and `netreg.ndscs.NoDak.edu' respectively.

If I add

        save -s netreg.ndsu.NoDak.edu

in the "Backup command:" for the `netreg-2.ndsu.nodak.edu' client, apply
it, and then probe the client, I still get:

* netreg-2.ndsu.nodak.edu:/ save: SYSTEM error: client `netreg' is not
properly configured on the NetWorker Server
* netreg-2.ndsu.nodak.edu:/ or `netreg' is not in the aliases list for
client `netreg-2.ndsu.nodak.edu'


Looking at the man page for `save' and with Robert Maiello's subsequent
email, it looks to me like this should be

        save -c client_name_as_configured_within_networker

e.g.

        save -c netreg-2.ndsu.nodak.edu

Using that, I'm able to bypass this problem, but you're right: I'm going
to need to do this for every client that I don't want to have the real
short name on the aliases list.

> It's a bit of a pain because you have to train your whole team to do
> this right all the time, but I dealt with this by writing a small
script
> to check client resources each day to catch any new records which were
> not set up correctly, and it's done the trick.

It is indeed a pain, and your script is a good idea.

Thanks much for your email!  It was very helpful!

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


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