George,
Others have answered most of the questions, I will address the OS issue.
Yes, you do need to go to RHEL 4 or 5 on the storage nodes. I would also
recommend going to Solaris 10 on the server.
I just finished upgrading a NW 7.2.2 on RHEL 3ES environment to NW 7.4.2
on
RHEL 5 environment. The process went flawlessly (essentially a fresh
install
across the board, just preserving /nsr), and as others pointed out
the key is to read through the Tech Guide and the Install Guide to make
sure
you catch all of the recommended items.
I can summarize my steps later, as I don't have access to the docs I put
together
while doing it at the moment.
Rodney
George Sinclair <George.Sinclair AT NOAA DOT GOV>
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
07/07/2008 05:34 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond
to
George Sinclair <George.Sinclair AT NOAA DOT GOV>
To
<NETWORKER AT LISTSERV.TEMPLE DOT EDU>
cc
Subject
[Networker] Advice on upgrading from 7.2.2?
Hi,
Sorry to beat on a topic that has probably been hammered many times
over, but I've been out of the loop for quite some time now, and need a
boost to get caught up.
We need to upgrade our 7.2.2 release (please, no laughs - ah, yeah),
running on Solaris 9. We use two snode servers (each runs RH Linux ES 3
with NW 7.2.2).
1. Can someone recommend which is the most recent stable NW release to
upgrade to?
We rely on cloning a lot. I remember hearing some mischief a while ago
about bugs with all that stuff in later releases and wanted to avoid any
such nightmares, hence one of the reasons for postponing, but that was
probably fixed a long time ago, though. Also, I've heard nwadmin is
gone, but doesn't take too long to get up and running with the new
interface (much better capabilities), whatever that is?
2. Will it be necessary to upgrade to 7.3.x first and then to 7.4.x?
3. Will we need to upgrade our clients immediately, say, before
upgrading the server? Would be kind of a pain to have to do that the
same day as the server upgrade.
4. Will we need to upgrade our snode OS, too, or just the NW version on
there?
5. Any particular gotchas on the upgrade? We have about 15 GB of free
space, and our largest index is about 2 GB, media database is about 257
MB with about 12 GB of total index usage.
6. Guess we'll need a new enabler code?
Last time we went from 6.x to 7.x we had some weirdness with one enabler
code that kept disabling itself. That was finally resolved with a no
expiration date code, and then we had another problem that was caused by
the old serial number (a legacy from the original release way back) not
matching the new SN format that was adopted in later releases. That was
finally fixed. Sheesh! Hope that frustration doesn't happen again this
go around.
Thanks.
George
--
George Sinclair
NOAA/NESDIS/National Oceanographic Data Center
SSMC3 E/OC3 Room 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
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
-----------------------------------------
E-mail Disclaimer:
The information contained in this e-mail, and in any accompanying
documents, may constitute confidential and/or legally privileged
information. The information is intended only for use by the
designated recipient. If you are not the intended recipient (or
responsible for the delivery of the message to the intended
recipient), you are hereby notified that any dissemination,
distribution, copying, or other use of, or taking of any action
in reliance on this e-mail is strictly prohibited. If you have
received this email communication in error, please notify the
sender immediately and delete the message from your system.
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
|
