Step by Rakesh Khandelwal:
First check release notes to make sure H/W and O/S you are about to use is supported or not. Release Notes for UNIX and Windows (http://support.veritas.com/docs/279259 )
Symantec’s Upgrade Guide, Version “B” ( http://support.veritas.com/docs/285590 )
Assuming you have already checked databse consistency and resolved any known or preexisting consistency issues or catalog inconsistencies
Step 1 : Prepare, Upgrade and Patcvh the Master Server
- Backup the catalogs
- In a c clustered environment, take NetBackup offline.
- Deactivate all policies.
- On Solaris Only, uninstall the old version of NetBackup.
- Upgrade the software:
- Stop all services.
- run the installation.
- Apply the latest maintenance packs.
NOTE : For Windows clustered environments, perform NetBackup upgrade installations from the system console, not from a Remote Terminal Services sessions.
Step 2: Populate the EMM database
- Ensure that the daemons or services and processes are running.
- Run nbpushdata -add on the ipgraded systems in the following order:
a) The host that was the 5.x Global Device Database host
b) All upgraded master servers
c) All upgraded 5.x Volume Database hosts - Restart the services/daemons.
- Run nbpushdata -modify_5x_hosts on all 6.0 master servers.
Step 3: Upgrade the NetBackup Remote Administration Console System and any addition components
1.Stop all services/daemons
2.Run the installation.
3.Apply the latest maintenace packs.
4.Restart the services/daemons.
5.Upgrade and add-on components.
6.Install the latest maintenance packs for the add-on components.
Step 4: Prepare, upgrade and Patch the Media servers
- On Solaris only, uinstall the old version of NetBackup.
- Upgrade the software:
a) Stop all services/daemons.
b) Run the instalation. - Apply the latest maintenance packs.
- Restart the services/daemons.
- Populate the EMM database:
nbpushdata -add
Step 5: Upgrade the clients
- Perform local or remote client upgrades.
- Install the latest maintenance packs.
Step 6: Complete and Test the upgrade
- Activate the policies
- Run test backup jobs.
- Backup the catalogs.
Additional Information from Dennis Strom:
here all the info I have on upgrading. I even included a link to this post since I really liked Rakesh’s post.
- run NCVU utility before upgrade
- run a catalog consistency check (bpdbm -consistency)
- is your catalog data in binary or ACSII? It is highly suggested to convert any NetBackup ACSII catalog information to binary mode using the cat_convert utility
- install pbx
- nbpushdata command after installing 6 and latest mp.http://forums.symantec.com/discussions/thread.jspa?threadID=73823&tstart=0 (Page Not Found)
- http://support.veritas.com/docs/283712
GENERAL ERROR: The nbpushdata command can fail if the
REQUIRED_INTERFACE entry exists in the vm.conf file
on a clustered NetBackup server - http://support.veritas.com/docs/283176
GENERAL ERROR: Running “nbpushdata” on Veritas NetBackup
(tm) 6.0 Maintenance Pack 2 (MP2) fails to push the globDB. - would really like to avoide downgrading
before upgrading once again described in
http://seer.support.veritas.com/docs/282327.htm - http://support.veritas.com/docs/285223
Welcome to the Veritas NetBackup ™ 6.0 Upgrade Portal! - http://support.veritas.com/docs/285590
Symantec’s Veritas NetBackup ™ 6.0 Upgrade Guide, Version “B” - Upgrading to Veritas NetBackup? 6.0
http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/285590.pdf - http://support.veritas.com/docs/277787
How to configure Hot Catalog Backups with Veritas NetBackup ™ 6.0. - http://support.veritas.com/docs/278610
DOCUMENTATION: VERITAS NetBackup ™ 6.0 “Hot Catalog Backup” will not include the jobs database. The jobs database will restart with a JobID of 1 after a Hot Catalog Backup recovery.
Other link:
