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 )
Upgrade Guide is your best friend in this regard -
Symantec's Upgrade Guide, Version "B" ( http://support.veritas.com/docs/285590 )
Following steps may help you build a project plan -
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 -
i) Backup the catalogs.
ii) In a c clustered environment, take NetBackup offline.
iii) Deactivate all policies.
iv) On Solaris Only, uninstall the old version of NetBackup.
v) Upgrade the software:
a) Stop all services.
b) run the installation.
vi) 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
i) Ensure that the daemons or services and processes are running.
ii) 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
iii)Restart the services/daemons.
iv) Run nbpushdata -modify_5x_hosts on all 6.0 master servers.
Step 3:Upgrade the NetBackup Remote Administration Console System and any addition components
i) Stop all services/daemons
ii) Run the installation.
iii) Apply the latest maintenace packs.
iv) Restart the services/daemons.
v) Upgrade and add-on components.
vi) Install the latest maintenance packs for the add-on components.
Step 4: Prepare, upgrade and Patch the Media servers
i) On Solaris only, uinstall the old version of NetBackup.
ii) Upgrade the software:
a) Stop all services/daemons.
b) Run the instalation.
iii) Apply the latest maintenance packs.
iv) Restart the services/daemons.
v) Populate the EMM database:
nbpushdata -add
Step 5: Upgrade the clients
i) Perform local or remote client upgrades.
ii) Install the latest maintenance packs.
Step 6: Complete and Test the upgrade
i) Activate the policies
ii) Run test backup jobs.
iii) Backup the catalogs.
<2.Also we have master servers in cluster configuration, I read that NOM does not work if Master is in cluster, is it correct?>
I don't think there is any such limitation but check latest release notes and NOM Getting started guide -
Veritas NetBackup (tm) Operations Manager (NOM) 6.0 Maintenance Pack 4 (MP4) Getting Started Guide Revision 1 for Windows and Solaris (last updated November 2006)
http://support.veritas.com/docs/285150
I know it is not recommended to configure on master server.64-bit OS is/are not supportd and even it does not support master server running on 64 bit.
NetBackup Operations Manager
See the following sections for supported NOM server platforms, managed NetBackup
master servers platforms, email clients, web browsers, and other software components.
Platforms Supported for the NOM Server
NetBackup Operations Manager server software can be installed on the following
operating system platforms:
NetBackup Managed Master Server Platforms Supported by NOM
NetBackup Operations Manager software supports management and monitoring of
NetBackup master servers on the following operating systems:
Operating System Supported Versions Notes
Microsoft Windows Microsoft Windows 2000 SP4 No 64 bit support
Microsoft Windows Microsoft Windows 2003 SP1 No 64 bit support
Sun Solaris Solaris 8 No 64 bit support
Sun Solaris Solaris 9 No 64 bit support
Operating System Supported Versions Notes
Microsoft Windows Microsoft Windows 2000 SP4 No 64 bit support
Microsoft Windows Microsoft Windows 2003 SP1 No 64 bit support
Sun Solaris Solaris 8 No 64 bit support
Sun Solaris Solaris 9 No 64 bit support