Veritas NetBackup™ Appliance Upgrade Guide

To install a downloaded release update using the NetBackup Appliance Shell Menu

1. Check to make sure that the following pre-upgrade tasks have already been performed:

   • All jobs have been stopped or suspended and all SLPs have been paused.

   • The Support > Test Software command has been run and it returned a Pass result.

   • All of the necessary RHEL plug-in packages have been copied into the appropriate location.

   See Pre-upgrade tasks for appliance upgrades.

2. Open an SSH session and log on to the appliance using the NetBackup Appliance Shell Menu.
3. To install the software release update, run the following command:

   Main_Menu > Manage > Software > Install patch_name

   Where patch_name is the name of the release update to install. Make sure that this patch name is the one that you want to install.

4. Monitor the preflight check and watch for any Check failed messages.

   • If no Check failed messages appear, you are prompted to continue to the next step to start the upgrade.

   • If any Check failed messages appear, the upgrade is not allowed. You must resolve the reported failures, then launch the upgrade script again so that the preflight check can verify that the failures have been resolved. Click on the UMI links (V-409-xxx-xxxx) for information about how to resolve the reported issues.

   • If any Check failed messages indicate that a RHEL version third-party plug-in was not found, you must obtain the plug-in from the appropriate vendor. Refer to the following topic for installation details:

     See Pre-upgrade tasks for appliance upgrades.

5. The upgrade may force the appliance to reboot several times.

   See Appliance behavior during upgrades.

   Note:

   For upgrades from 2.6.1 or 2.6.1.x, the system may reboot several times during the upgrade process. After the first reboot, the NetBackup Appliance Web Console and any SSH-based connections to the server are unavailable until the reboot process has completed. This condition may last 2 hours or more, depending on the complexity of the appliance configuration. It is important that you do not attempt to reboot the appliance during this time. You can use the Veritas Remote Management interface (IPMI) to view the system reboot status. In addition, you may view the logs under /log or wait for the appliance to send an email upon completion of the upgrade process.

6. After the upgrade has completed and the disk pools are back online, the appliance runs a self-diagnostic test. Refer to the following file for the test results:

   /log/selftest_report_<appliance_serial>_<timedate>.txt

   If SMTP is configured, an email notification that contains the self-test result is sent.

7. Complete this step only if your backup environment includes SAN client computers.

   The Fibre Channel (FC) ports must be re-scanned to allow any SAN client computers to reconnect to the Fibre Transport (FT) devices. The re-scan must be done from the NetBackup CLI view on the appliance.

   To re-scan the FC ports:

   • Enter the following command to see a list of NetBackup user accounts:

     Manage > NetBackupCLI > List

   • Log on to this appliance as one of the listed NetBackup users.

   • Run the following command to rescan the FC ports:

     nbftconfig -rescanallclients

   • If any SAN clients still do not work, run the following commands on each of those clients in the order as shown:

     On UNIX clients:

     /usr/openv/netbackup/bin/bp.kill_all

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

     On Windows clients:

     <install_path>\NetBackup\bin\bpdown

     <install_path>\NetBackup\bin\bpup

   • If any SAN clients still do not work, manually initiate a SCSI device refresh at the OS level. The refresh method depends on the operating system of the client. Once the refresh has completed, attempt the nbftconfig -rescanallclients command again.

   • If any SAN clients still do not work, reboot those clients.

     Note:

     If you have SLES 10 or SLES 11 SAN clients that still do not work, Veritas recommends upgrading the QLogic driver on those clients. For the affected SLES 10 clients, upgrade to version 8.04.00.06.10.3-K. For the affected SLES 11 clients, upgrade to version 8.04.00.06.11.1.

8. Refer to the following topic for tasks that may be required after the upgrade has completed: