|
I've done two upgrades in the last two weeks, one Windows and one Linux Master.
Pulling and working from several document sources had my desk looking like I was trying to cram for a test so I created an internal checklist in an attempt to consolidate everything I believed was needed for the upgrade. For DR purposes, use by other staff, and because Management loves documentation I spent more time than usual in creating this check list which is attached.
My stagging upgrade environment: W2K 5.1 MP60A Master, 4 SuSE 9 SP3 Media Servers - 5.1 MP6, 1 P2000 and P3000 Library, Remote Media Host and SSO.
Both upgrades went well, but each had caveats, here is the Windows upgrade summary:
1. Much preparation, including the on line and off line help from Symantec (see doc).
2. Windows upgrade ok, nbpushdata completed with soft errors (3 1/2 hrs for the push).
3. Linux upgrade ok, nbpushdata very fast. Only issue was with the media install times, using our own script, we changed that from 35 to 7 minutes (see doc).
4. Three Post upgrade issues with Windows, only one with Linux. I suggest one might review note #5 for the Linux post upgrade issue (see doc for all post upgrade issues and notes).
My worst upgrade experience was from 4.x to 5.x which sounded similar in pain for those who went from 5.x to 6.0. All in all, this one went well and I'm more at ease about upgrading our other production systems later in April.
I think Tony posted early about a Hot Backup problem with error code 800, we also encountered that problem, but in our case when we obtained the solution from Symantec we could no longer duplicate the error. That solution was:
SOLUTION/WORKAROUND:
Stopped services
Renamed the SYNC file in Netbackup\db\config
Started services
Reconfigured Off-line catalog
REFERENCE:
As mentioned by others, I would highly recommend a fallback plan and use it as a test environment for a 6.5 pre-install to get an idea of what you'll run into when you upgrade your production systems.
PLEASE, don't consider the attached anything more than my checklist based on my experience (here it comes), so the disclaimer is use at your own risk - I guarantee your experience will be different.
Scott
| 
