On Jul 7, 2008, at 6:34 PM, George Sinclair wrote:
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?
You might as well go to 7.4 SP2 since its the most recent version and
it seems relatively stable. I plan to upgrade from 7.4 SP1 to it in a
week or so.
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?
Sorry, I cannot comment on cloning, as it is something we don't do here.
2. Will it be necessary to upgrade to 7.3.x first and then to 7.4.x?
No.
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.
There's no rush to upgrade the clients, but you should plan on doing
that upgrade over the next few months in order to take advantage of
NetWworker's new features.
4. Will we need to upgrade our snode OS, too, or just the NW version
on there?
The OS on your storage nodes is pretty old. Check EMC's software
compatibility matrix for info on if NetWorker 7.4 SP2 is compatible,
but it probably can't hurt to update the OS on your storage nodes. You
will definitely need to upgrade the NetWorker software on your storage
nodes to the same version that's on your NetWorker server.
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.
After you install 7.4 SP2, run the following command
nsrports -C 0-0
See the nsrports man page for an explanation of what this does. Do the
same on all the clients after you upgrade them. Restart the NetWorker
software in order for this command to take effect.
6. Guess we'll need a new enabler code?
Yup, an update enabler code is required. Take a look at the release
notes for 7.4 SP2 or the installation instructions. The update enabler
code appears there.
Be sure to read the release notes carefully prior to upgrading.
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
|
