Has anyone performed an upgrade from 6.5.2a to 6.5.4?
Updated: 18 Jun 2010 | 7 comments
If so, were there any issues that you came across? Anything to watch out for? I believe we will be performing this upgrade fairly shortly.
Our OS is Solaris 10.
Any bumps in the road to expect would be appreciated.
discussion Filed Under:
Comments
Assisted a customer with
Assisted a customer with upgrade on Solaris 10 recently.
Experienced the failure documented in this TechNote: seer.entsupport.symantec.com/docs/325408.htm
Just keep the original 6.5 install media handy. The solution is to remove VRTSpbx and VRTSicsco and reinstall before re-attempting the patch install.
All went fine after that.
Just perform the normal precaution steps - ensure you have a catalog backup.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
I faced with this problem
I faced with this problem http://www.symantec.com/connect/blogs/netbackup-654-upgrade-using-sun-patches-important
It's to hard to know all possible problems but you have to crete a "plan B" if everything will go by wrong way. Most upgrades goes normally.
Not from 6.5.2a
But I did document an upgrade from 6.5.1 to 6.5.4 on a Solaris 9 Master.
Regards Andy
"It's not too late to panic ..."
Thanks for the help folks
I will definately be sure to remove pbx before the upgrade. I looked around before making the thread and nothing popped up, so I probalby would not have found that issue until it was staring me in the face during the actual upgrade.
We're down to d-day
h-hour
I really hope this goes smoothly.
so far so good
*knocks on wood
The binaries were installed without issue. I'm performing my test backups now.
Late Breaking News and Known Issues
Rjrumfelt,
Be sure to review the 6.5.4 late breaking news, TN 324985, known issues are documented there. Review the known issues, if you're suffering from one or there other, be sure to acquire the EEBs related to the fixes.
Would you like to reply?
Login or Register to post your comment.