|
This may be the last two weeks of
experience talking here.
We upgraded to 6.5.1 and starting having very long queue
times. Investigation showed that there was a fairly consistent 30-45
minutes between when a job "requested resources" and when Netbackup actually
granted resources. Adding 30 minutes to every job, when you run almost
4000 jobs per day, was killer.
It was suggested that this was a problem that was fixed in
6.5.2. So I upgraded to 6.5.2 and the queue time problem went away.
It replaced it with a bug, though, were all my Oracle backups with a 24x7
application schedule would die at midnight.
July 28th I opened a ticket, described the e-track number
& the tech note number and it took until Friday 8/8/08 to get the now
infamous nbpem patch.
Today was the first day I really had a chance to look at
the results - queue times are back at 30-45 minutes for resource requests AND
the 196 errors are still occurring at night.
I just reverted 6.5.2 nbpem binary so I only have one
problem to deal with.
Three phone calls & an email to support today and I've
yet to receive a callback.
It's my opinion, beaten into me, I'd suggest, that this
6.5.2, 6.5.2a, & 6.5.2a-patch has been a bad set of
binaries.
(Sol 8 master, extensive use of STU-groups, 20 media
servers)
-M
On Wed, Aug 13, 2008 at 2:51 PM, <Mark.Donaldson AT cexp DOT com>
wrote:
6.5.2a
(and 6.5.2) is brain damanged software. A very bad release and
I've been
fighting several issues with it.
We had to install an nbpem EEB but since that was installed, it's been
working fine for us. We run about 2500 jobs per day on a Solaris master
server with nearly a dozen media servers. It may not have been a perfect
release for everybody at release date, but it's a far cry from "a very bad
release".
I
suggest you revert, if you can, and if not contact Veritas support.
I disagree with this advice. Your first action should be to
contact Support. If they can't help you move forward, THEN consider
reverting. Don't blindly revert, first because it's harder than it looks,
and secondly, there may be some data you need to capture to send to Symantec so
that they can fix any possible bugs you're experiencing. You don't want to
get bitten by the same thing next time you upgrade and there's no guarantee that
somebody else will work with Symantec it to get it
fixed.
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP,
SCSE
ewilts AT ewilts DOT org
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
