The upgrade is relatively straight-forward, but there are a number of 
things that work very different.  Your old methods will stick work in 
3.2/3.4.  A simple upgrade without taking advantage of new things like 
multistreaming and ALL_LOCAL_DRIVES would be a waste.  An example of this 
would be using '/' and 'Cross Mount Points," instead of ALL_LOCAL_DRIVES 
and multistreaming.

I'd skip 3.2 and go right to 3.4.  Otherwise, you'll be behind again in 
less than six months.

If you have any scripts that use NBU commands, they might break in 
3.4.  Some things that I remember:
1. A minor format change to bpdbjobs (3.4)
2. A minor format change to vmcheckxxx (3.4)
3. The addition of VMD5 comment lines to some config files that didn't have 
them before. (Came in 3.4)
4. Multistreaming breaking bpstart_notify/bpend_notify if you use it. 
(There are workarounds, though.)


At 11:50 AM 5/10/2001 +1000, Terry Newnham wrote:

>Hi
>
>We have a product which combines the Veritas products Volume Manager
>2.5, Media Manager 3.1.1, Netbackup 3.1.1 and HSM 3.1.1. We run them on
>a Solaris 6 platform. The server acts as both a HSM server and a backup
>server for several clients. What will put pressure on us to upgrade
>Netbackup will be the necessity to backup Solaris 7 and 8 platforms
>(plus other operating systems that may come on board here).
>
>I was wondering if anybody here had made such an upgrade and what kind
>of issues they'd encountered. Things like:
>
>Is the upgrade path complicated or straight-forward ?
>
>Do any of the other Veritas products have to be upgraded to work with NB
>3.2 ?
>
>Is NB 3.2 the best option compared to the more recent releases ?
>
>Terry
>
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

---
W. Curtis Preston
Principal Consultant for Storage Designs, your storage experts
Webmaster: http://www.backupcentral.com Phone: 760 631 7991