In regard to: Re: [Networker] Upgrading server OS and NW version at the...:

So if we re-do the OS, and I install 64bit NW (hopefully NW 7.6 SP2,

if it

comes out within the next couple weeks),

The DR procedure assumes you're going to install exactly the same

version

of NetWorker, but you're also talking about changing versions and the

ABI

at the same time.  That's not generally advised during a DR.  If

you're

very, very comfortable with NetWorker and the DR procedure you can
probably pull it off.

But why, I wonder?

In a true disaster, you don't want to be increasing the challenge by
throwing any unnecessary variables into the mix.

Well, yes, I know *that*.

You're asking the question, so I'm trying to be precise, both for your
benefit and for the benefit of anyone that may find this thread in the
archives down the road.

LOL I meant, why would 32 v 64 bit make a
difference,

In a perfect world, it wouldn't make a difference, but this is a
complicated software package we're talking about here.  You can take the
"no worries" approach and just assume that it doesn't make a difference,
but people that are responsible for business continuity tend to be
cautious about making assumptions like that.

There are plenty of minor things that I've encountered over the years
that should never have made a difference with how NetWorker functions,
but they did.

if I am not running a full system recover of the NW server,
and am instead just recovering the mm database.

I thought that going from 32bit to 64bit was supported (perhaps not in the

I hope it is and I believe it should be.  Right now, I don't *know*
whether it is, though, and apparently you don't either.  Until such a
time as I can read actual confirmation from EMC that it's supported, I'm
going to assume it's *not*.

exact sequence I have outlined, but moving platforms from 32bit to 64bit,
possibly staying in the same version, surely can't mean that a customer is
destined to lose potentially years of mm history ...).

One could make the argument that moving platforms from Solaris to Linux or
Linux to Windows also shouldn't mean that a customer is destined to lose
potentially years of mm history.

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