If it’s true that 6.5.2a is only addressing the aforementioned "all jobs running a full after upgrade" issue then why am I being told that 6.5.2a will fix an issue that I have with my catalog backups (occasional failure with status code 2 and catalog email notifications randomly stopping and starting) ? 

 

I’m currently running 6.5.1 on a Solaris 10 x86 master and those are the only issues we’re having problems with.

 

Mark Glazerman

Desk: 314-889-8282

Cell: 618-520-3401

P please don't print this e-mail unless you really need to

 

 

The solution for queued jobs 196'ing at midnight is an engineering binary from support not 6.5.2a. As Comp_geek_gal pointed out the 6.5.2a release was only to resolve the "all jobs running a full after upgrade" issue. As of now we are upgrading our Solaris masters to 6.5.2a with two EEBs, one for nbpem (queued fail at midnight) and the other for nbjm (dup issue). We have completed 8 large upgrades so far with no additional issues as of yet (knock on wood).

Beth Sexton



Elizabeth Sexton

"Martin, Jonathan" <JMARTI05 AT intersil DOT com> Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu 07/26/2008 07:24 AM

To:        <veritas-bu AT mailman.eng.auburn DOT edu>         cc:                 Subject:        Re: [Veritas-bu] 6.5.2 & 6.5.2A  BEWARE!!!

I upgraded from 6.5.2 to 6.5.2a to resolve the issue with queued backups failing at midnight when their window is open past midnight.  As of right now, it looks like that is still very much an issue.  I’ve got a load of backup jobs that fire at 8:00PM Friday night with a 2 day window.  As of midnight, anything in a queued state failed with error 196.  Guess I’ll be re-opening the case with Symantec. /sigh.
 
I haven’t been able to perform any VCB backups yet, but according to the support engineer 6.5.2a was supposed to have a few fixes for that as well.
 
-Jonathan
 

 

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Haskins, Steve
Sent: Saturday, July 26, 2008 12:03 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 6.5.2 & 6.5.2A BEWARE!!!
 
All; especially Windows Netbackup admins,
 
  I upgraded my Windows test Netbackup 6.5.1 environment  to 6.5.2 then 6.5.2A. Problem with 6.5.2 in Downing a drive in that it would down the wrong drive. 6.5.2A no problem (test environment again).
 I upgraded my production environment this past week from 6.5.1 to 6.5.2A and PEM would not start so obviously scheduled backups would not start and I had to roll back to 6.5.1 which was painful. Two media servers I had to uninstall/reinstall Netbackup server software and reconfigure.
  Found one case on the web where another peer had the same problem. I opened a case with Symantec and they strongly advised me to not install 6.5.2 and just wait for 6.5.3. this fall instead of trying to correct 6.5.2A. As reported to me the main fixes in 6.5.2A were to resolve admin console issues which I have experienced.
 
FYI, if you get an error message stating to close all processes and try again when updating or rolling back a MP rename the Netbackup.dll in the                                   %installpath%\Netbackup\Bin folder as long as no other processes besides standard Netbackup services are running.
 
Regards
 _______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.