I believe you have to do the "pkgrm" on both master and media servers, there
isn't a way that I know of to push media server binaries from the master,
that only works for clients.

Last time I upgraded from 3.2 -> 3.4, here's what I did (I only had one
master and no media servers).

Stop all daemons.

Run a ufsdump of the system just in case (otherwise Curtis would yell at
me).

Run the "pkgrm" on SUNWnbp and SUNWmmgr answering "yes" to the upgrade
question.

Run the "pkgadd" of the new software.

Check to make sure your startup/shutdown scripts are still okay then reboot
(just for fun).

If you modified any of the scripts in NBUHOME/bin or NBUHOME/bin/goodies,
then make sure to modify the new versions.

Upgrade any clients running NetBackup database agents, making sure to
upgrade the agent too.  In my experience, the 3.2 agents will work, but you
get some non-obvious errors in your logs.

Upgrade all NT clients to 3.4 because a number of us have encountered
problems with NT 3.2 clients backing up to a 3.4 Solaris master.

Steve

-----Original Message-----
From: veritas-bu-admin AT Eng.Auburn DOT EDU
[mailto:veritas-bu-admin AT Eng.Auburn DOT EDU]On Behalf Of Speier, Guy J - CNF
Sent: Wednesday, November 01, 2000 9:31 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] NetBackup upgrade


Hello,

Strictly a Solaris 2.6 environment, what is the procedure to upgrade a slave
server?  I am thinking this:

1) Stop daemons on master & slave.
2) pkgrm on master (answer yes to "is this part of an upgrade"?)
3???) Do I do the same on the slave, or do I "push" the new binaries from
the master?

Can anyone share their upgrade procedures with me?

thank you,
Guy
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu