I don't know.  Why spend time upgrading your hardware and testing your
new hardware only to then have to then upgrade your software?  I think
you could argue it both ways.  My current thought is that the way you're
suggesting seems more correct, but I'm not sure if I could argue it
really strongly.  I'm curious if someone else could help me do that.

I said:

> I completely agree with not doing them at the same time.  Any thoughts
> as to which way is better?
>
> 1. Upgrade NetWorker
> 2. Wait a few backup cycles
> 3. Upgrade hardware
>
> Or
>
> 1. Upgrade hardware
> 2. Wait a few backup cycles
> 3. Upgrade NetWorker


Stan said:
>The second option is what makes the most sense for anyone who is  
>about to upgrade to new hardware. Why spend time upgrading NetWorker  
>software on old hardware and testing it only to
>move to new hardware after the testing period is over?

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