So what is the verdict on 220.127.116.11?
I am looking to upgrade 18.104.22.168 to 22.214.171.124
W2K8 master, using vstorage API backups of 5.0 esx, and KMS for managing LTO4 encryption keys, and DDBoost for data domain OST disk pools.
I want to update esx to 5.1 and allow for SQL 2012 and windows server 2012.
I would say if you aren't having the issue with NBSL, I would not patch it.
The only damage we see with it is a Java UI that won't load completely and failures with OpsCenter to connect to the Master. Jobs continue to run and kick off as expected, we just can't manage them through the UI.
On Sun, May 19, 2013 at 11:27 PM, Lavelle, Michael F <Michael.F.Lavelle AT abbott DOT com>
126.96.36.199 has been rescheduled for late June. The new CEO of Symantec is aware of declining reliability and increases in EEB creation.
We are running three NetBackup 188.8.131.52 domains under RedHat 5 (2.6.18-348) and VCS 5.0. We are running with two EEBs installed:
ET3106719 – the ghost jobs issue which replaces nbjobd
ET3156426 – image catalog filesystem grows dramatically thru failure to properly clean the old files
This replaces nbpem & bpdbm
We also need to upgrade past VCS 5.0. VCS had been masking the “largefiles” option of VxFS and the BMR_DATA.db file grep to 2 GB in the primary
UNIX domain. Instance crashed since it could not extend the BMR database. Recovered OK – thanks to Matthew in Australia. We also have a work around for the VCS mask of “largefiles”.
We really need 184.108.40.206 for Windows Server 2012 support. This is really not funny. This proliferation was needed before the end of the year.
That if flunked out of 220.127.116.11 and requires 18.104.22.168 is bad enough. The funny thing is that the 22.214.171.124 release is now being delayed because the new Symantec CEO smells the quality of what has been released in recent years (needed features, but new and unexpected
bugs along with the new code), and is demanding actual engineering qualification of code releases. Here’s hoping NBU 7.6 is delayed longer and for the same good reasons.
If you were me, and I already am running with two EEBs, and have not experienced the NBSL crash and core dump, would you prophylactically apply
EEB ET3123001 on top of the others? I do not want to run a regression testing lab for Symantec.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Rusty Major
Sent: Thursday, May 16, 2013 2:26 PM
To: Kohli, Vidit
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Post upgrade 126.96.36.199 issues?
Don't wait, there is a fix for the NBSL issues. You might want to call support to make sure you get the right EEB for your issue as there is more than one.
On Thu, May 16, 2013 at 12:15 PM, Kohli, Vidit <vidit.kohli AT blackrock DOT com> wrote:
There is major bug in 188.8.131.52 as per Symantec, so better wait for 184.108.40.206
nbsl experiences a memory leak which results in a core dump.
The following versions of NetBackup are affected by this issue:
The nbsl daemon crashes intermittently and creates a core dump. It was observed that memory consumed by nbsl was constantly growing, and when it reached somewhere around 4GB, nbsl
This issue is scheduled to be addressed in the following release:
NetBackup 7.5 Maintenance Release 6 (220.127.116.11)
Unsure for Windows, for Linux/64-bit and
Yes there is a problem with ghost jobs: (you will see 100s-1000s of jobs Active but they really complete)
This EEB fixes that issue:
I am starting to plan for a 7.5 upgrade from 6.5.6 in an environment that I am consulting at for the next few months. Has anyone run into any major bugs or issues with 18.104.22.168
after the upgrade? I am running Windows x64 as my master with multiple NDMP filers and no media servers.
THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE PRIVILEGED. If this message was misdirected, BlackRock, Inc. and its subsidiaries, ("BlackRock") does not waive any confidentiality or privilege. If you are not the intended recipient,
please notify us immediately and destroy the message without disclosing its contents to anyone. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. The views and opinions expressed
in this e-mail message are the author's own and may not reflect the views and opinions of BlackRock, unless the author is authorized by BlackRock to express such views or opinions on its behalf. All email sent to or from this address is subject to electronic
storage and review by BlackRock. Although BlackRock operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu