Networker

Re: [Networker] NW server RHEL4 32bit to RHEL5 64 bit upgrade

2011-09-28 19:25:09
Subject: Re: [Networker] NW server RHEL4 32bit to RHEL5 64 bit upgrade
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 28 Sep 2011 18:21:28 -0500
In regard to: [Networker] NW server RHEL4 32bit to RHEL5 64 bit upgrade,...:

Just got off a chant with support that essentially recanted that part of
the installation guide as 'being cautious'.

He said essentially that 32->64 bit did not actually require any special
procedures if the file system stayed the same.

I'm at a loss to understand that statement.

And that those procedures
in the install document were there only for when upgrading the networker
packages' bitness, not the OS' bitness.

That seems to contradict the statement about it being filesystem related.

I personally agree more with this second statement, which makes me wonder
if I misunderstood your initial question.  Are you changing the OS ABI
(32 bit to 64 bit) *but* keeping NetWorker as a 32 bit app?  If you are,
and you can find recent confirmation from EMC that you have a supported
configuration, then I don't think you need to go through the DR procedure.
If you're not converting NetWorker itself from 32 bit to 64 bit, I don't
believe there should be any need to reload the media database or CFIs.

As I said in my initial response to your question, when I went from RHEL 4
to RHEL 6.1, I *did* convert NetWorker from 32 bit RPMs to 64 bit RPMs,
and followed what was spelled out in the install guide, which was to do
the DR.

Now I'm not sure what to believe. I think I might follow what I think is
the letter of the install guide's law, which is to recover the media db
and the server's index on the new system, and just make sure that I have
a good snapshot of the other indexes...

When in doubt, it's always safer to err on the side of caution, and in
this case, that would be the DR.

If you skip the DR, let the list know how it goes, either way.  I'm sure
it will be helpful (either as a timesaver, or as a cautionary tale!) to
many others down the road.

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