| Title: | NetWorker |
| Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
| Moderator: | DECWET::RANDALL .com::lenox |
| Created: | Thu Oct 10 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 750 |
| Total number of notes: | 3361 |
My customer is runnig 3.2A NSR. We are starting to look at how to
upgrade. We have almost 40 clients and 2 servers. My suggestion is to
fisrt upgrade the development server to 4.2C, but leave the clients
at 3.2A. When that looks stable, we will upgrade the Production server
to 4.2C
When that is all stable we will finally upgrade the clients to 4.2c
We do NOT trust, nor could we carry out, a concurrent upgrade of
everything at once.
My customer wants a specific answer as to these versions being
commpatiable.
Any problems with 3.2A clients calling 4.2c servers? The customer has
seen some item on the DEC external WEB page that he reads to mean 4.2C
servers can only work with 4.2C clients.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 592.1 | DECWET::SDY | Look out!!..Support Rookie sez... | Fri Apr 18 1997 12:11 | 22 | |
Any problems with 3.2A clients calling 4.2c servers? The customer has
seen some item on the DEC external WEB page that he reads to mean 4.2C
servers can only work with 4.2C clients.
While there shouldn't be any problems with 3.2A clients using a 4.2C server,
I would warn you that V4.2C requires OS Kernel patches. If the customer does
not intend (in the near future) to use the HSM features, then they might
be better off (reduced amount of transition work) using V4.2B + patch 12.
The items he's probably seen are the kernel hook requirements for the clients
since V4.2C is a DU 4.0 or better release only. If he has DU 3.2x based clients
he'll have to run NetWorker V4.2B on them (or stick with V3.2A, ugh =)
Your listed plan of attack (for upgrading) sounds very reasonable. The only
thing I might suggest, is that prior to upgrading the production server to the
newer version of NetWorker, you might want to consider upgrading a few of the
clients that are pointed at the developmental server to the newer version of
NetWorker. This will give you experience on what your production cut over would
entail. It would also be easier to back out if you find client upgrade problems.
steve.
| |||||
| 592.2 | DECWET::RWALKER | Roger Walker - Media Changers | Fri Apr 18 1997 15:11 | 4 | |
Also be very carefull to check out the patch list. There have been some problems in the past that have been fixed. It shouldn't be a big deal if it is done with care and verification (like doing test recovers on the clients before and after each step). | |||||
| 592.3 | LEXSS1::GINGER | Ron Ginger | Tue Apr 22 1997 11:53 | 7 | |
Thanks
This customer (Osram Sylvania) has been hit with some kind of nsr bug
on every version upgrade we have made. That is why they are waiting so
long and going so slow on this one. We will follow the suggestion to
try a few clients before the production upgrade.
| |||||
| 592.4 | DECWET::ONO | Software doesn't break-it comes broken | Fri Apr 25 1997 11:48 | 4 | |
A way to avoid the kernel patch issue is to use NetWorker V4.2B plus patch 12. Wes | |||||