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