Upgrade NB 6.0mp7 to 7.1

[pursch]

I have a few questions regarding this upgrade (please see lines starting with >>>>> below).

This is my proposed upgrade procedure (short version, trimmed of a lot of detail).

I've used SORT, read the NB 7.1 Unix install guide, NB 7.1 release notes, etc. I just have a few questions, plz see below.

To upgrade netbackup server from versions 6.x or 7.x to 7.1
-----------------------------------------------------------

Step 1 Review the upgrade portal checklist (on SORT), upgrade docs, and installation documents.
Step 2 Do a full catalog backup.
Step 3 Validate/verify the consistency of the NetBackup EMM and BMR databases.
Step 4 Deactivate all NetBackup policies, storage lifecycle policies, disk staging storage units, and media servers.
Step 5 Upgrade master server and media server to 7.1.0.
Step 6 Do a full catalog backup.
Step 7 Upgrade the master server and media server to 7.1.0.3.
Step 8 Do a full catalog backup.
Step 9 Upgrade the clients to 7.1.0.3.
Step 10 Upgrade any installed NetBackup add-on products (such as language packs).

Details
-------

Step 1 Review the following:

- the upgrade requirements for unix servers (page 67 of nb 7.1 install guide, online).
- the server installation requirements for unix systems (page 20 of nb install guide, online).
- the netbackup 7.1 release notes document (in the distribution or online).
- the changes in netbackup 7.0 (page 13 of nb install guide, online).
- the netBackup mixed version support doc (page 16 of nb install guide, online).
- the list of known issues (http://www.symantec.com/docs/TECH153422)
- the netbackup 7.1 documentation (http://www.symantec.com/docs/TECH154178)
- the netbackup planning and performance tuning guide (http://www.symantec.com/docs/DOC4483)
- the netbackup 7.1 admin guide for unix ( http://www.symantec.com/docs/DOC3650 and http://www.symantec.com/docs/DOC3651)

Step 2. Back up the existing NetBackup databases.

- do a full catalog backup using the NetBackup Admin Console (jnbSA).

Step 3. Validate/verify the consistency of the NetBackup EMM and BMR databases.

- Log on as the root user on the server.

- Validate/verify the consistency of the NetBackup EMM and BMR databases.
( follow http://www.symantec.com/business/support/index?page=content&id=TECH126758
     and http://www.scribd.com/doc/30638519/Consistency-Check-for-NBU-6-x-Databases-for-Upgrade-to-NBU-7.0 )

-- Stop all NetBackup services.
-- Once all services have stopped, start only the ASA Service.
-- # /usr/openv/netbackup/bin/nbdbms_start_stop start
-- Perform a consistency check, issuing the following commands:
-- # cd /usr/openv/db/bin
-- # ./nbdb_admin NBDB.db -validate -full

If any inconsistencies are found, they will be reported.
For a consistent database, no errors reported will be returned as output.

>>>>>>> -- Should I start all NetBackup services here? I think I need to, in order to use the Admin Console to do Step 4.


Step 4. Deactivate all NetBackup policies, storage lifecycle policies, disk staging storage units, and media servers.


Step 5. Upgrade the master server and media server.

Step 5.a. Ensure that you have license keys for all of the NetBackup servers, clients,
options, and agents that you ordered.

>>>>>>> -- I received no keys from Symantec for 7.1. I have my 6.0 keys. Will they suffice for the upgrade? Two people on the forum say yes.

Step 5.b. Close the NetBackup Administration Console.

Step 5.c. For Solaris servers only, let the install script
remove the 6.x or 7.x versions of all add-on products and database agents.

>>>>>>> -- Should I shutdown all NetBackup processes here (/etc/init.d/netbackup stop; /usr/openv/netbackup/bin/bp.kill_all) ?

Step 5.d. For Solaris systems, all of the NetBackup scripts that you may have modified
are removed when you complete the following step.

Perform each of the following tasks in the order as shown:

- Save any files that you have modified and want to keep.
- Remove the current NetBackup server package by using the appropriate command:

-- For version 6.0: pkgrm VRTSnetbp
-- For versions 6.5 and later: pkgrm SYMCnetbp

The following prompt appears:

Are you doing this pkgrm as a step in an upgrade process?

Enter y.


Step 5.e. Untar the distribution.

(per http://www.symantec.com/business/support/index?page=content&id=TECH154080 )

# /usr/sfw/bin/gtar --version

Version 1.16 or higher is required.
if your version of gtar is lower, download and install the latest from sunfreeware in /usr/sfw.

cause the Netbackup installation install script to use /usr/sfw/bin/gtar instead of /usr/bin/tar:

# cd /usr/sfw/bin
# ln -s ./gtar tar
# echo $PATH
# setenv PATH /usr/sfw/bin:$PATH
# which tar
# tar --version

# cd yourpath
# cp NetBackup_7.1_Solaris_Sparc64.tar.gz /tmp
# cd /tmp
# gunzip NetBackup_7.1_Solaris_Sparc64.tar.gz
# tar -xf NetBackup_7.1_Solaris_Sparc64.tar


Step 5.f. Navigate to the location where the installation images reside and run the installer:

# cd /tmp
# ./install

Follow the prompts in the installation script to install the NetBackup server binaries.


Step 5.g. Apply the workaround for windows policy delays, if necessary:

(per http://www.symantec.com/business/support/index?page=content&id=TECH156810 )


Step 5.h. After all servers are upgraded, reactivate the following in the order as shown:

- All media servers
- All disk staging storage units
- All NetBackup policies
- All storage lifecycle policies


Step 6. Do a full catalog backup.

>>>> Should I let 7.1 run for a few days before proceeding to 7.1.0.3?

Step 7. Upgrade the master server and media server to 7.1.0.3.


Step 7.a Populate the install dir.

>>>>> Should I use gnu tar here, as I did in Step 5 above?

# cd /usr/sfw/bin
# ln -s ./gtar tar
# echo $PATH
# setenv PATH /usr/sfw/bin:$PATH
# which tar
# tar --version

# cd yourpath
# cp NB_CLT_7.1.0.3.tar /tmp
# cp NB_7.1.0.3.solaris.tar /tmp

# cd /tmp
# tar xf NB_7.1.0.3.solaris.tar
# tar xf NB_CLT_7.1.0.3.tar

Step 7.b Per http://www.symantec.com/business/support/index?page=content&id=TECH174107 :

1) Close the NetBackup user interfaces.

   - Make sure the NetBackup server has no active jobs running (for example, backups, restores, or duplications).
   - If a database agent is installed, such as Oracle, ensure that the database services are stopped.

>>>>>>> -- Should I shutdown all NetBackup processes here (/etc/init.d/netbackup stop; /usr/openv/netbackup/bin/bp.kill_all) ?

2) Install NB_7.1.0.3 and NB_CLT_7.1.0.3 Maintenance Release binaries.

        cd /tmp
        /bin/sh NB_update.install

   NOTE: Selecting the server Maintenance Release automatically installs the
         client Maintenance Release if the client (CLT) .gz file and the README
         exist in the installation directory. The server install fails if the
         (CLT) .gz file and the README are not present and the CLT update has
         not been previously installed.

3) The NB_update.install script prompts you to restart daemons.
   Otherwise, after the update installation has completed, run:

        /usr/openv/netbackup/bin/bp.start_all

Step 8. Do a full catalog backup.

Step 9. Upgrade the netbackup clients to 7.1.0.3.

Step 10. Upgrade any installed NetBackup add-on products (such as language packs).

[Marianne · Accepted solution]

I MUST compliment you on your EXCELLENT preparation!
(Wish everyone would do that...)

It seems that NBCC was removed from the Upgrade Portal - I would add this as part of step 1: http://www.symantec.com/docs/TECH67840

To answer your questions:

>>>>>>> -- Should I start all NetBackup services here?
No harm in swapping steps 3 and 4.

>>>>>>> -- I received no keys from Symantec for 7.1. I have my 6.0 keys. Will they suffice for the upgrade?
They will suffice for the upgrade, but you won"t be able to use new features that were introduced in 6.5, 7.0 and 7.1.
Why not apply for your new keys on the Licensing Portal?
https://licensing.symantec.com
For additional information on the Symantec Licensing Portal, please refer to the User’s Guide located at the following URL:
https://licensing.symantec.com/acctmgmt/home/Jump.jsp
For further assistance with upgrading the licenses, please contact the Symantec Enterprise Customer Care Team for your region:
http://www.symantec.com/business/support/assistance_care.jsp

>>>>>>> -- Should I shutdown all NetBackup processes here
Yes.

>>>> Should I let 7.1 run for a few days before proceeding to 7.1.0.3?
Good idea. Be aware of possible issues as documented in Late Breaking News.

>>>>> Should I use gnu tar here, as I did in Step 5 above?
Correct.

>>>>>>> -- Should I shutdown all NetBackup processes here
The patch installation script will automatically look for active processes and stop them.

GOOD LUCK!!

[pursch]

the upgrade from nb 6.0mp7s0 to nb 7.1.0.4 was successful!

special thx to Marianne van den Berg for her excellent suggestions, two of which were essential:

- use NBCC to check catalog consistency before upgrading

- contact Symantec licensing support to obtain nb 7.1 keys and use them when upgrading

i downloaded NBCC 7.5 from Symantec and used it on my 6.0mp7s0 installation, discovering that my catalog was inconsistent. i then opened a case with Symantec and worked with support for 2-3 weeks before finding the cause and resolving the inconsistencies.

i also contacted licensing support and obtained the necessary 7.1 key info for my upgrade. when i upgraded, i opted to enter my 6.0 keys (use the current license keys) and then my 7.1 keys (add additional keys). all licensed features are working ok in 7.1.0.4.

i first upgraded to 7.1, ran for a week, then went to 7.1.0.4.

the upgrade to 7.1 went smoothly. my previously published procedures were adequate, after adding a step to use NBCC per Marianne's advice. i also needed to do a "pkgrm VRTSnbora" before i did the "pkgrm VTRSnetbp", because i had the netbackup oracle agent installed in my 6.0 installation. i also was able to remove all of my win pc images and policies, so did not need to workaround the known delay bug that the update installer has when processing win pc policies.

[Marianne]

Great stuff and well done!