08-27-2008 09:53 AM
Hello,
Looking for comments, concerns, opinions on Netbackup 6.5.2. Boss heard some bad things about this M.P. and wanted to get others opinions on the version.
Thanks,
The Dude
08-27-2008 10:03 AM
yes he is correct a lot of issues with 6.5.2, go to 6.5.2a and request for the nbpem bin to symantec, then you will be fine.
regards
08-27-2008 10:13 AM
I have upgraded to 6.5.2a (unix master/media)
I have not seen anything bad yet.
but I don't use a LOT of what is avail. I just do plain backups and use the exchange, don't use any other database items.
08-27-2008 11:48 AM
@omar Villa wrote:yes he is correct a lot of issues with 6.5.2, go to 6.5.2a and request for the nbpem bin to symantec, then you will be fine.
Which of the problems did nbpem bin fix? Was it the "running a full, even though it should have been a differential". From the screaming in the forum, it does not fix the calendar crossing the 00:00.
I now have a project to change all my calendar based schedules to frequency based - just so that I can upgrade to 6.5.2a without too much heartburn.
08-27-2008 12:20 PM
@Ron Cohn wrote:
Which of the problems did nbpem bin fix? Was it the "running a full, even though it should have been a differential". From the screaming in the forum, it does not fix the calendar crossing the 00:00.
I now have a project to change all my calendar based schedules to frequency based - just so that I can upgrade to 6.5.2a without too much heartburn.
There IS an nbpem fix which correctly crosses midnight. Open a case and reference this TechNote:
BUG REPORT: Queued backups with 24x7 windows are failing at midnight with status code 196.
http://support.veritas.com/docs/305656
I know, I just posted this in another thread. I'm big on repetition.
08-27-2008 12:27 PM
Chris,
I am following this on multiple threads too!
Now for the next question: Does the hotfix have to be uninstalled BEFORE applying the 6.5.3 update? I know in the MS world, we have to do this. How about the Symantec world?
08-27-2008 12:48 PM
Yes, you can install 6.5.3 on top of any 6.5.2+EEB environments...as well as any other 6.5 GA or 6.5.x environments. (Or at least, that's the way it's always been in the past and I have no indications it will be any different with this release.)
To answer your other question in the other thread, I don't know about "right" and "wrong" but the behaviour should be as it always was...including in 6.5.1. ;)
08-27-2008 12:51 PM
08-28-2008 05:48 AM
08-29-2008 07:05 AM
Just installed my 4th !!!! binary patch in 6.5.2a
and I'm still havin' 2 calls open.
looks more that I'm a beta tester
Still regret the day that I had to leave version 5....
Peter