Networker

Re: [Networker] Problems renaming NW 7.4.2 server in Windows

2008-08-08 17:47:32
Subject: Re: [Networker] Problems renaming NW 7.4.2 server in Windows
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 8 Aug 2008 16:42:36 -0500
In regard to: Re: [Networker] Problems renaming NW 7.4.2 server in Windows,...:

If so, do I need to
delete "admnlts003", and remake it, using that client ID?

Yup.  Or, create it with a different name.  If NetWorker can resolve
the name, it should be fine creating the client as something like

    admnlts003-old

That way, you can have both the old data and the data you've backed
up since converting to the new server.

AH HA! I sense salvation. I can live with that - I could make up fake IPs
for all the "-old" names (to be honest, it's probably only 2 or 3 hosts
that I woulod *probably* restore from, based on my experience in the last
year). I could make them up in the hosts file, so NW would find it, and
then I should just do a redirected restore, from the "-old" to the new.

Sure.  That's what we do when we need to bring an old client back that's
no longer in the DNS.

I'm not sure if "redirected restore" is the same thing I'm thinking of,
but we generally set up the host access within NetWorker so that
"new-client" has access to "old-client", and then administrator
(or root) on "new-client" can just browse the "old-client" and pull
data back.

As long as NetWorker doesn't mind that the name used to be "admnlts003",
and now is "admnlts003-old" (but has the same client ID, and links the
"scanner -i" info to "admnlts003-old".

It shouldn't mind, because this is the procedure you use to change a client
name.

Have you tried that? Does it work?

We've renamed clients recently, which is very similar to what you're
doing.  I haven't tried this exact procedure in a few years, but it
worked back then.

Tim, if that works, remind me that I owe you a keg or two ....

Just send it to Davina, or Darren, or Rodney Wines, or a dozen other
people from this list that have saved my butt over the years or explained
how things *really* work when I was confused or new to some bit of
functionality in NetWorker.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  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