Hi Carl,
We are an all Windows shop so it may (or may not) be related to
Win2k3 server. I have a feeling that issue I was seeing (and the one you
seem to be seeing as well) is stemming from an issue somewhere between the NBU
Job Details and the point where Aptare gathers that info FROM NBU. The
odd thing is , it’s happening to only 1 client. I would have
expected to see it from a lot more. This client isn’t even unique.
It has 160GB of storage with about 700,000 files, no big deal. I have
many more clients with similar specs that are reporting just fine.
I hold 90days worth of NBU info so Support thought it may have
been the large amount of data I have that needs to be pulled into Aptare.
So when I was working with support, they had me replace the bpdbjobs.exe with a
replacement that would knock that info down to 24hrs. Well, they gave me a
replacement file that was for Unix not windows so obviously when the jobs ran
again, errors started appearing (the 0 Bytes and NULL values). After
trying again with no success, I reverted back the bpdpbjobs and associated
files and things were normal for a few days; even the one client that was reporting
the wrong amount of data seemed to be cured. Then I upgraded (thinking
this might help stabilize things) and the 0 / NULL values for the JOBIDs
started to occur again. I have a feeling that there was some resident
evil lurking, and when I upgraded and restarted the services, it appeared
again.
Support was very quick to respond to my request yesterday and I
have some good techs working on the issue. It looks like the issue of 0
or NULL valued JOBIDs has stopped and it looks like it appeared only after the upgrade
and my restarting the Aptare and Oracle services. Unfortunately, my
Aptare database is filled with these bogus jobs so Support wrote a sql script
to run in Oracle that will remove them from the database so my reports and
dashboards don’t look like a sea of red. With my second go of
Support, I have received some superior help and advice. I truly applaud
their efforts in trying to help solve my issue.
So far, the upgrade has been fine after that initial issue.
I’m still monitoring it but will let you know if I see any other issues
or benefits.
Hope that helps Carl.
Phil.
From: ckstehman AT pepco DOT com
[mailto:ckstehman AT pepco DOT com]
Sent: Friday, June 15, 2007 7:54 AM
To: Philip McDougal
Cc: veritas-bu AT mailman.eng.auburn DOT edu;
veritas-bu-bounces AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Aptare and NBU not reporting properly ...
Philip
We recently
upgraded to NBU6.0MP4. Aptare 5.2.06 continued to work fine. About
two weeks later
I upgraded
Aptare to 6.0.14. Since that time I have noticed missing MBytes
information at times, and
missing and
inconsistent File List and Stirage Unit information from the Netbackup
Job Detail drill down.
I am
collecting from two master servers, one is Solaris, the other is Windows 2003.
Interestingly the missing
File List
information is always from the Windows server, the Solaris server is fine. I
have not really
checked the
MBytes for accuracy to any level of detail. I am working with Aptare
support on these issues.
I am thinking
about upgrading to 6.0.19, but your experience raises converns.
Regards
Carl
=============================
Carl Stehman
IT Distributed Services Team
Pepco Holdings, Inc.
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com
"Philip
McDougal" <pmcdougal AT calamos DOT com>
Sent by:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
06/14/2007
06:29 PM
|
To
|
<veritas-bu AT mailman.eng.auburn DOT edu>
|
cc
|
|
Subject
|
[Veritas-bu]
Aptare and NBU not reporting properly ...
|
|
Hey guys,
Has anyone
who is running Aptare and NBU ever had issues where the job summaries are
reporting the wrong information?
I had an
issue 2 weeks ago where a client (1 client out of 100 some odd) was reporting a
fraction of the amount actually backed up. It backed up and was reported
as successful and the number of files backed up were correct but Aptare would
only report ~30GB out of the 150GB that was getting backed up daily. I
worked with support on it, and of course, it magically disappeared after a week’s
worth of frustrating work with Support.
Today, I
upgraded to 6.0.19 and as soon as I finished upgrading, the job summaries
for today started filling up with errors. Well, no jobs ran but I have tons of
Job Summaries that have either a 0 for the JOBID or a NULL value.
It’s totally blowing my SLAs and SOX audits to pieces.
Has anyone
else experienced this and is there a way to remove the NULL values for the
JOBIDs?
Thank you!
Phil McDougal
CALAMOS INVESTMENTS CANNOT ACT UPON, AND WILL NOT ACCEPT, ANY TIME-SENSITIVE
ELECTRONIC MESSAGES, SUCH AS TRANSACTION ORDERS AND FUND TRANSFER INSTRUCTIONS.
ALSO, FOR YOUR PROTECTION, PLEASE DO NOT SEND ANY IDENTIFYING INFORMATION, SUCH
AS ACCOUNT NUMBERS OR SOCIAL SECURITY NUMBERS, THROUGH THE INTERNET.
CONFIDENTIALITY NOTICE: This message is intended only for the use of the
individual or entity to which it is addressed and may contain information that
is confidential . If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, distribution or copying of this
communication is prohibited. Please notify the sender immediately if this
message was transmitted in error. Thank you._______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This
Email is intended solely for the use of the person(s) to which it is addressed.
If you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies. PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication. PHI will not accept any liability in respect of such communications.