Hi tim
You need to contact EMC for a rehosting on your Networker server.
Med vennlig hilsen / Best Regards,
Otto V. Gudjonsson
Senior Technical Account Manager
Exello Norge AS - Kronprinsensgate 1 - N.0251 Oslo - NORWAY
+47 24 13 08 00 - http://www.exello.com
Følg oss på Twitter: http://twitter.com/ExelloNorge
(Kopier alltid support AT exello DOT no på tekniske henvendelser)
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Tim Mooney
Sent: 1. februar 2012 20:13
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] replacing NSR peer information on a NetWorker server
All-
Yesterday I replaced the hardware on our primary NetWorker server. The server
OS also went from RHEL 5.7 to RHEL 6.2. The NetWorker version stayed the same
(7.6.2.5), but I did convert from 32 bit to 64 bit NetWorker install.
As described in the installation guide, that meant going through the disaster
recovery procedure. I'm well-versed in that procedure and it went fine, as did
reconfiguring the jukebox (the control port changed SCSI address) and
recovering the client file indexes.
Much to my surprise, though, the disaster recover procedure does *not* bring
back the previous "nsrladb" when it recovers the other resources.
This means that the server certificate used as part of the "peer"
authentication changed.
Surprisingly, only about two dozen of our 125+ clients failed their backups
last night because of the change in the server certificate, but now I'm in a
quandary.
I've now been through one (incremental) cycle with the new/regenerated server
cert. Can I simply replace the new certificate (or entire nsrladb) with the
one recovered from backups, or is that just going to cause problems for other
clients?
If I controlled all of the clients that failed, I would just delete their
server peer information and let it be regenerated, but unfortunately many of
the clients are SLA backup customers, so I have no access to the client systems.
Any thoughts on whether replacing the nsrladb on a NetWorker server with a
recovered copy is a good idea, or if that's just asking for trouble?
Thanks,
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
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
|
