Netbackup is backward compatible, not forward compatible (as far as support
is concerned, though some things _may_ work).

If you have mixed versions of nbu masters and media servers, manage them
from an admin station with the same revision level (major and minor) as the
highest level master/media server you have.

Also, if you add entries to bp.conf or registry to allow new remote admin
stations, some of the guis work fine without a service stop&start and others
do not (from the new remote admin station).  If you have mixed nt/unix
masters be sure name resolution is not an issue, since netbackup uses
machine name comparisons to do its authentication (setup hosts files and or
fwd/rev dns).

A.S.

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of
benr AT cuddletech DOT com
Sent: Tuesday, October 16, 2001 4:21 PM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NB Windows Admin GUI problems


Here's the scoop.  My manager likes playing with the Netbackup windows admin
GUI (you know where you aren't a client, but you want to have control over
several diffrent NB servers).
He can connect to several of our 3.2GA servers and everything is fine, but
when he connects to a 3.4 server he gets odd errors.  Whats really odd is
that he can look at the activity monitor, he can get to the media manager.
But if he pulls up the Policy Manager or the Device Manager he gets either
an "Invalid Server" or "Unable to connect" error.  Both of which are hogwash
because the server is up (and often in use) with no problems, and he can
definalately connect to it since he can view the jobs.

Veritas support is NO help at all.  Any thoughs would help.

Thanx

benr AT cuddletech DOT com


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