This is a multi-part message in MIME format.
--Boundary_(ID_+AispvPTh5dt9sUrbhupyA)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
I don't have the problems you're describing with the Java GUI at all.
You definitely need something more than a sparc 5, though. What you're
describing sounds like a screwed up physical configuration in more ways
than one. I'm not sure what's wrong with the wizard, but if it won't
finish, that's a serious problem that someone should troubleshoot.
Perhaps a rebuild of the OS would help.
As to the routing problem, how else would they design it? How would you
expect to administer a system that you can't telnet/rsh/ssh to, anyway?
-----Original Message-----
From: Paul Winkeler [mailto:pwinkeler AT pbnj-solutions DOT com]
Sent: Friday, September 20, 2002 3:11 PM
To: W. Curtis Preston; 'Hampus Lind'
Cc: 'Veritas maillista'
Subject: RE: [Veritas-bu] upgrade 3.4.1 to 4.5 (warning about SAP agent
compatibility)
Curtis
It is good to hear others are having more success. We cannot even get
the Java GUI to go through the device discovery wizard! As a result
only the Job Activiy view is useful. It continuously updating "KBytes
Written" fields place such a load on the X server it makes the GUI
unresponsive. One might argue that we should get a faster console than
a SparcStation 5, but you know, that was more than adequate before.
The corrupt, inaccurate job status data is so rife and rampant it is
hard to believe you are not having any problems. Even my small single
machine, single drive test setup shows inconsistencies: Jobs start
positioning before mounting tapes, show as positioning when they are
writing, it is just a mess. This is not an aesthetic problem: take a
look at the output of bpdbjobs -all_columns and you'll see why the GUI
shows what it does. Heck, even the /usr/openv/netbackup/db/jobs/trylogs
directory is rife with <jobid>.t files showing the same inconsistent job
information!
The windows GUI is gorgeous to look at but its requirement that the PC
is a registered as a server and be visible on the entirely separate,
private backup network poses a problem in and of itself: this network
only exists in the data-room, no where else! Again, a bone-headed
design if you ask me: we are trying to get operators out of the
dataroom! We may go to enhanced authentication to get around the SERVER
entries problem but the netowrk routing problem remains.
So sofar the fact that the jobs appear to be running more reliably is
completely overshadowed by the fact that no one can really tell how much
improved the underlying backup engine is. A real shame indeed.
I really do look forward to the faster catalog searches the next time I
need to restore. But try restoring a single archive log from an SAP
backup using the GUI. BEEEP, sorry you can no longer do this! Veritas
feels you should use brrestore for this so the SAP type has been removed
from the types of images you can browse for in a restore session.
Sorry for the ranting nature of this message but man, oh man, am I tired
off all this after having been told the upgrade would be a no-brainer.
My customer's opinion of NetBackup ( and now me too ) has dropped
considerably...
PaulW
-----Original Message-----
From: W. Curtis Preston [mailto:curtis.lists AT backupcentral DOT com]
Sent: Friday, September 20, 2002 5:55 PM
To: 'Paul Winkeler'; 'Hampus Lind'
Cc: 'Veritas maillista'
Subject: RE: [Veritas-bu] upgrade 3.4.1 to 4.5 (warning about SAP agent
compatibility)
I understand what you're saying about the SAP problem, but I don't agree
with your characterization of everything else.
1. I LOVE the new Java Admin GUI on UNIX.
It's all in one GUI, much simpler to understand than the previous
GUIs, etc.
It's a little slow when displaying it to a remote X session, but
there's no reason to do that.
You have two choices:
A) Install the Java console on the remote machine if it's Unix/Linux.
B) Install the admin console if it's Windows. I prefer this over the
Java console, only for a few pieces of functionality.
2. As to remote admin from a Windows box, you can use enhanced
authentication/authorization instead of the bp.conf method.
3. I have seen massive improvement in search capabiity even in small
image catalogs. I say upgrade!
4. I've seen the "bad job info." It's a minor asthetical problem, not
data corruption. I'm sure they'll fix it soon.
(What I've seen is one job reported twice, for example.)
-----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 Paul
Winkeler
Sent: Friday, September 20, 2002 5:59 AM
To: Hampus Lind
Cc: Veritas maillista
Subject: RE: [Veritas-bu] upgrade 3.4.1 to 4.5 (warning about SAP agent
compatibility)
Hampus
We just went through such an upgrade at a client site and here is a
quick summary of our experience:
1) Actual upgrade is smooth enough (don't forget to immediately apply
the current Service Pack, number 1)
2) Try and leave clients alone as they will work fine and you'll have a
harder time trouble shooting if you change everything all at once.
3) If you use the SAP agent anywhere; those machines clients and their
agents MUST be upgraded to 4.5 as the 3.4 SAP agent will NOT work with a
4.5 master!
4) The Unix based Java Administrative GUI sucks wind. Badly. Not only
that but it its activity monitor reports plain old wrong job status
information. As does the detail behind bpdbjobs. We haven't run with
the Windows administrative console much yet because it requires that
these PCs be listed as servers in the bp.conf file. All NBU systems at
this site sit on a private network and we cannot route to/from it to
where the adminstrative PCs are located. (Stupid design on Veritas'
behalf if you ask me...)
5) Unless your image catalog is huge, don't bother converting it. Just
let the old images stay in ascii format.
6) The new binary job database, although it content is badly hosed, is
reported on nice and fast, FWIW.
If the client hadn't needed storage unit grouping so storage units could
be prioritized we would never have upgraded.
Just my $.02
-----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 Hampus Lind
Sent: Friday, September 20, 2002 4:14 AM
To: Veritas maillista
Subject: [Veritas-bu] upgrade 3.4.1 to 4.5
Hi.
I`am about to carry out a upgrade from Netbackup DataCenter 3.4.1 to
4.5.
Has any one had problem with this? Or maybe some good pointers?
We have Netbackup DataCenter 3.4.1 master and media server in the same
hp-ux 11.00 server. Out clients are everything from NetWare, Windows,
solaris, hpux to informix database agents.
Tanks in advance
Hampus
--Boundary_(ID_+AispvPTh5dt9sUrbhupyA)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2719.2200" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=154491523-20092002><FONT face=Arial color=#0000ff size=2>I
don't have the problems you're describing with the Java GUI at all. You
definitely need something more than a sparc 5, though. What you're
describing sounds like a screwed up physical configuration in more ways than
one. I'm not sure what's wrong with the wizard, but if it won't finish,
that's a serious problem that someone should troubleshoot. Perhaps a
rebuild of the OS would help.</FONT></SPAN></DIV>
<DIV><SPAN class=154491523-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=154491523-20092002><FONT face=Arial color=#0000ff size=2>As to
the routing problem, how else would they design it? How would you expect
to administer a system that you can't telnet/rsh/ssh to, anyway?
</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid;
MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Paul Winkeler
[mailto:pwinkeler AT pbnj-solutions DOT com] <BR><B>Sent:</B> Friday,
September 20,
2002 3:11 PM<BR><B>To:</B> W. Curtis Preston; 'Hampus Lind'<BR><B>Cc:</B>
'Veritas maillista'<BR><B>Subject:</B> RE: [Veritas-bu] upgrade 3.4.1 to 4.5
(warning about SAP agent compatibility)<BR><BR></FONT></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2>Curtis</FONT></SPAN></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff size=2>It
is good to hear others are having more success. We cannot even get the
Java GUI to go through the device discovery wizard! As a result only
the
Job Activiy view is useful. It continuously updating "KBytes Written"
fields place such a load on the X server it makes the GUI unresponsive.
One might argue that we should get a faster console than a SparcStation 5,
but
you know, that was more than adequate before.</FONT></SPAN></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff size=2>The
corrupt, inaccurate job status data is so rife and rampant it is hard to
believe you are not having any problems. Even my small single machine,
single drive test setup shows inconsistencies: Jobs start positioning before
mounting tapes, show as positioning when they are writing, it is just a
mess. This is not an aesthetic problem: take a look at the output of
bpdbjobs -all_columns and you'll see why the GUI shows what it does.
Heck, even the /usr/openv/netbackup/db/jobs/trylogs directory is rife with
<jobid>.t files showing the same inconsistent job
information!</FONT></SPAN></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff size=2>The
windows GUI is gorgeous to look at but its requirement that the PC is a
registered as a server and be visible on the entirely separate, private
backup
network poses a problem in and of itself: this network only exists in the
data-room, no where else! Again, a bone-headed design if you ask me: we
are trying to get operators out of the dataroom! We may go to enhanced
authentication to get around the SERVER entries problem but the netowrk
routing problem remains.</FONT></SPAN></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff size=2>So
sofar the fact that the jobs appear to be running more reliably is completely
overshadowed by the fact that no one can really tell how much improved the
underlying backup engine is. A real shame indeed.</FONT></SPAN></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff size=2>I
really do look forward to the faster catalog searches the next time I need to
restore. But try restoring a single archive log from an SAP backup
using
the GUI. BEEEP, sorry you can no longer do this! Veritas feels
you
should use brrestore for this so the SAP type has been removed from the types
of images you can browse for in a restore session.</FONT></SPAN></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2>Sorry for the ranting nature of this message but man, oh man, am I
tired off all this after having been told the upgrade would be a
no-brainer. My customer's opinion of NetBackup ( and now me too ) has
dropped considerably...</FONT></SPAN></DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=720375521-20092002><FONT face=Arial color=#0000ff
size=2> PaulW</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> W. Curtis Preston
[mailto:curtis.lists AT backupcentral DOT com]<BR><B>Sent:</B> Friday,
September
20, 2002 5:55 PM<BR><B>To:</B> 'Paul Winkeler'; 'Hampus Lind'<BR><B>Cc:</B>
'Veritas maillista'<BR><B>Subject:</B> RE: [Veritas-bu] upgrade 3.4.1 to
4.5
(warning about SAP agent compatibility)<BR><BR></FONT></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff size=2>I
understand what you're saying about the SAP problem, but I don't agree with
your characterization of everything else.</FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2>1.
I LOVE the new Java Admin GUI on UNIX. </FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2> It's all in one GUI, much simpler to
understand than the previous GUIs, etc. </FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2> It's a little slow when displaying it to a remote
X session, but there's no reason to do that. </FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2> You have two choices:</FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2> A) Install the Java console on the remote machine if
it's Unix/Linux.</FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2> B) Install the admin console if it's
Windows.
I prefer this over the Java console, only for a few pieces of
functionality.</FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2>2.
As to remote admin from a Windows box, you can use enhanced
authentication/authorization instead of the bp.conf
method.</FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2>3.
I have seen massive improvement in search capabiity even in small image
catalogs. I say upgrade!</FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2>4.
I've seen the "bad job info." It's a minor asthetical
problem, not data corruption. I'm sure they'll fix it
soon.</FONT></SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2> (What I've seen is one job reported twice, for
example.)</FONT> </SPAN></DIV>
<DIV><SPAN class=061214921-20092002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid;
MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of
</B>Paul
Winkeler<BR><B>Sent:</B> Friday, September 20, 2002 5:59 AM<BR><B>To:</B>
Hampus Lind<BR><B>Cc:</B> Veritas maillista<BR><B>Subject:</B> RE:
[Veritas-bu] upgrade 3.4.1 to 4.5 (warning about SAP agent
compatibility)<BR><BR></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>Hampus</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>We just went through such an upgrade at a client
site and here is a quick summary of our experience:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>1) Actual upgrade is smooth enough (don't forget
to immediately apply the current Service Pack, number
1)</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>2) Try and leave clients alone as they will work
fine and you'll have a harder time trouble shooting if you change
everything all at once.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>3) <STRONG>If you use the SAP agent anywhere;
those machines clients and their agents MUST be upgraded to 4.5 as the
3.4
SAP agent will NOT work with a 4.5 master!</STRONG></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>4) The Unix based Java Administrative GUI sucks
wind. Badly. Not only that but it its activity monitor
reports
plain old wrong job status information. As does the detail behind
bpdbjobs. We haven't run with the Windows administrative console
much yet because it requires that these PCs be listed as servers in the
bp.conf file. All NBU systems at this site sit on a private network
and we cannot route to/from it to where the adminstrative PCs are
located. (Stupid design on Veritas' behalf if you ask
me...)</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>5) Unless your image catalog is huge, don't
bother converting it. Just let the old images stay in ascii
format.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>6) The new binary job database, although it
content is badly hosed, is reported on nice and fast,
FWIW.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>If the client hadn't needed storage unit
grouping
so storage units could be prioritized we would never have
upgraded.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650514612-20092002>Just my $.02</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]<B>On Behalf Of
</B>Hampus Lind<BR><B>Sent:</B> Friday, September 20, 2002 4:14
AM<BR><B>To:</B> Veritas maillista<BR><B>Subject:</B> [Veritas-bu]
upgrade 3.4.1 to 4.5<BR><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Hi.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I`am about to carry out a
upgrade
from Netbackup DataCenter 3.4.1 to 4.5.</FONT></DIV>
<DIV><FONT face=Arial size=2>Has any one had problem with
this? Or maybe some good pointers? </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>We have Netbackup DataCenter 3.4.1 master
and media server in the same hp-ux 11.00 server. Out clients are
everything from NetWare, Windows, solaris, hpux to informix database
agents.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Tanks in advance</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial
size=2>Hampus</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
--Boundary_(ID_+AispvPTh5dt9sUrbhupyA)--
|
