NetBackup Appliance 2.7.3 Release

NetBackup Appliance 2.7.3 Release

Article: 100038710
Last Published: 2017-05-26
Ratings: 1 3
Product(s): Appliances

Description

NetBackup Appliance Software Update 2.7.3 README


NetBackup appliance software version 2.7.3 supports direct upgrades for appliance models 5220, 5230, and 5330 that currently use software versions 2.6.1, 2.6.1.1, 2.6.1.2, 2.7.1, or 2.7.2.

Note:
 NetBackup 5200 appliances cannot be upgraded to software versions 2.7.1 and later.

Starting with NetBackup appliance software version 2.7.1, Red Hat Enterprise Linux (RHEL) replaces the SUSE Linux Enterprise Server (SLES) operating system. Before you upgrade appliances with versions 2.6.1, 2.6.1.1, or 2.6.1.2, certain pre-upgrade tasks must be performed to help ensure a successful upgrade. For complete details, see the NetBackup Appliance Upgrade Guide.

For additional information about new features, product fixes and enhancements, known issues, and the current release content included in this software update, refer to the NetBackup Appliance Release Notes.

 

TABLE OF CONTENTS

  • Product Dependencies
  • Downloading and Installation Instructions
  • Attachments
 

Product Dependencies

  • For appliances that are configured as a media server, this upgrade requires a NetBackup Appliance 2.7.3 master server appliance or a traditional NetBackup 7.7.3 master server. Master servers must be upgraded before media servers.

    Note: If the appliance is used to communicate with a deduplication appliance over Fibre Channel, make sure that the deduplication appliance software is at version 1.4.3 or later.

  • This release supports a direct upgrade from versions 2.6.1, 2.6.1.1, 2.6.1.2, 2.7.1, or 2.7.2. For complete details about upgrades to version 2.7.3, refer to the NetBackup Appliance Upgrade Guide.

  • After a successful upgrade, rollback from this version of NetBackup appliance software is not supported.

  • Before you begin the upgrade process, make sure that there are no backup jobs currently running or scheduled to run during the upgrade.

  • During installation of this release update, all NetBackup services and web services are shut down and restarted automatically.

Make sure that the NetBackup master server is turned on and running throughout the duration of the media server appliance upgrade. In addition, make sure that the NetBackup processes are started on both the master server and the media server.


Downloading and Installation Instructions

The following procedures describe how to download and install the NetBackup appliance version 2.7.3 release update. Instructions are included for both server and client packages. Client packages are not included with the server packages and must be downloaded separately, as described in the procedures that follow.


Manually downloading NetBackup appliance server packages and client packages

If the automated download method failed, use this procedure to download the release update files.

Perform this task from a computer that can access the Internet and can also communicate with the appliance. Internet access is required to download the release update files from the Veritas Support web site to the appliance.

Due to the unique file name extensions of the split server packages, monitor your browser behavior closely during the file downloads. When you right-click a file link and select  Save link as... or  Save target as..., make sure that the file names retain the  .xof3 extension. For example:  .2of3.


To download software release updates or client packages to an appliance using a CIFS or NFS share

1. Open an SSH session and log on to the appliance as an administrator using the NetBackup Appliance Shell Menu.

2. To open an NFS or a CIFS share, enter the following command:
     Main_Menu > Manage > Software > Share Open

3. Map or mount the appliance share directory as follows:

  -Windows
  Map the following appliance CIFS share on your computer:
   \\< appliance-name>\incoming_patches

 Windows systems prompt you for the admin user name and its corresponding password.

  -UNIX
  Mount the following appliance NFS share:
   mkdir -p /mount/<appliance-name>
 mount < appliance-name>:/inst/patch/incoming/mount/< appliance-name>

4. This step describes the package file names for the release update packages and the client packages. After reviewing the names, continue with the remaining steps to download the files.

-Release update packages
NB_Appliance_N_< release-version>.x86_64-tar-split.1of3
NB_Appliance_N_< release-version>.x86_64-tar-split.2of3
NB_Appliance_N_< release-version>.x86_64-tar-split.3of3
Where < release> is the software release number and < version> is the version number of the software release. For example: 2.7.3-1.

To verify that the downloaded release update packages have the same MD5 or SHA1 checksums as those posted on the Veritas Support web site, do the following:
  • Enter the following URL for the Veritas Support site where the release updates and the client packages are posted: https://www.veritas.com/content/support/en_US/58991.html
  • In the How to... section, click the download link for the posted software update.
  • On the README page, in the right column, click Attachments.
  • Verify that the checksums shown in the pop-up window match the downloaded file checksums.

-Client packages
SYMC_NBAPP_addon_nbwin_< release>-< date>.x86_64.rpm
Or:
SYMC_NBAPP_addon_nbclient_< platform>-< release>-< date>.x86_64.rpm
Where < platform> is the client platform operating system, < release> is the software release number, and < date> is the NetBackup client package date. For example:

SYMC_NBAPP_addon_nbclient_HP-UX-IA64-release-20150910.x86_64.rpm

5. Use one of the following commands to join (and extract) the release update .rpm files:

-Windows
copy /b NB_Appliance_N_<release-version>.x86_64-tar-split.1of3+NB_Appliance_N_<release-version>.x86_64-tar-split.2of3+NB_Appliance_N_<release-version>.x86_64-tar-split.3of3 NB_Appliance_N_<release-version>.tar

Note: This command must be entered as one string. Make sure that the only space in the name is after  .3of3 . In addition, < release> is the software version number and < version> is the posted version number.
 
Use Windows WinRAR utilities to uncompress the NB_Appliance_N_< release-version>.tar file. The resulting files are as follows:
  • SYMC_NBAPP_update-<release-version>.x86_64.rpm
  • update.rpm.md5_checksum
  • update.rpm.sha1_checksum

-UNIX
cat NB_Appliance_N_<release-version>.x86_64-tar-split.1of3<space>NB_Appliance_N_<release-version>.x86_64-tar-split.2of3<space>NB_Appliance_N_<release-version>.x86_64-tar-split.3of3 | tar xvf -
Where < release> is the software release number and < version> is the version number of the software release. For example: 2.7.3-1.

Note: This command is one string. In this example, there is one space between each split package that is identified with a "<space>".

The resulting files are as follows:
  • SYMC_NBAPP_update-<release-version>.x86_64.rpm
  • update.rpm.md5_checksum
  • update.rpm.sha1_checksum
Note: To extract packages on UNIX systems, Veritas recommends that you use GNU tar version 1.16 or higher instead of tar. See the following article for more information about extracting images:  https://www.veritas.com/docs/000012145

6. For UNIX systems, run one of the following commands to compute the checksum value for the .rpm file:
md5sum SYMC_NBAPP_update-<release-version>.x86_64.rpm
Or:
sha1sum SYMC_NBAPP_update-<release-version>.x86_64.rpm

Verify that the checksum value matches the content of the update.rpm.md5_checksum  file  or the update.rpm.sha1_checksum file.

7. Copy this release update or client package .rpm to the mounted share.
Note: During the copy process, do not run any commands on the appliance. Doing so can cause the copy operation to fail.

8. After you have successfully copied the release update or client .rpm package into the mounted share, unmap or unmount the shared directory.

9. On the appliance, enter the following command to close the NFS and the CIFS shares:
Main_Menu > Manage > Software > Share Close

Note: If you run any of the following commands before you close the share, the downloaded release update or client package is moved from the share directory location to its proper location. However, you must still run the Share Close command to ensure that the NFS and the CIFS shares are closed.
  • List Version
  • List Details All
  • List Details Base
  • Share Open
  • Share Close
10. To list the available release updates or client packages on the appliance, enter the following command and note the name of the downloaded files:
Main_Menu > Manage > Software > List Downloaded

Running this command validates and moves the release update or the client package from the share directory to its proper location. You are not notified that this move has occurred. If the command shows a status of Pending, wait a few minutes and try it again.


Installing a NetBackup appliance software update

After you have downloaded a software update to the appliance, it can be installed from the NetBackup Appliance Shell Menu using this procedure.

When you perform an appliance upgrade, Veritas recommends that you take precautions to avoid loss of connectivity. Any loss of connectivity during an upgrade results in failure. The computer that you use to upgrade the appliance should be set up to avoid the following events:

  • Conditions that cause the computer to go to sleep
  • Conditions that cause the computer to shut down or to lose power
  • Conditions that cause the computer to lose its network connection


The following describes operational behavior during and after an appliance upgrade:

  • Web services are unavailable during most of the upgrade process, which prevents access to the NetBackup Appliance Web Console. To view the upgrade progress during this time, run the following command from the NetBackup Appliance Shell Menu:
Main_Menu > Manage > Software > UpgradeStatus
  • The appliance restarts several times while the upgrade is in progress. After the first restart, the NetBackup Appliance Web Console and any SSH-based sessions to the server are unavailable until all restarts have completed. During this time, you can use the Remote Management Interface (IPMI) to view the system restart 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.
  • When you upgrade a NetBackup appliance, the FTMS server is restarted automatically. As a result, the Fibre Channel (FC) ports must be rescanned to allow any SAN client computers to reconnect to the Fibre Transport (FT) devices. The last step in the following procedures describes how to rescan the FC ports after the upgrade has been completed.


Use the following commands to view the available release updates, see which update is currently installed, and see the current version of the appliance:

  • Main_Menu > Manage > Software > Check
This command checks the Support website for the latest software update.
  • Main_Menu > Manage > Software > List Downloaded
This command shows the available appliance release updates.
  • Main_Menu > Manage > Software > List Details All

This command shows all of the software packages that are currently installed on the appliance.

  • Main_Menu > Manage > Software > List Details Base

This command shows all of the software packages that were installed on your appliance during the factory installation.

  • Main_Menu > Manage > Software > List Version

This command shows the appliance version, the NetBackup version, and the appliance build date.
 

To install the downloaded appliance release update

1. For upgrades from 2.6.1, 2.6.1.1, or 2.6.1.2, 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 returned a Pass result.
  • All of the necessary RHEL plug-in packages have been copied into the appropriate location.
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 matches the downloaded file name.

4. Monitor the pre-flight check and watch for any  Check failed messages. Proceed as follows:
  • 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.
  • 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. For complete details, see the NetBackup Appliance Upgrade Guide.
5. Watch the onscreen progress of the upgrade to see an estimated completion time. To see the current status of the upgrade, enter the following command:
    Main_Menu > Manage > Software >UpgradeStatus

6. The upgrade may force the appliance to restart several times. 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.

Note: The system may restart several times during the upgrade process. After the first restart, the NetBackup Appliance Web Console and any SSH-based connections to the server are unavailable until the restart process has completed. This condition may last two hours or more, depending on the complexity of the appliance configuration. It is important that you do not attempt to restart the appliance during this time. You can use the Remote Management interface (IPMI) to view the system restart 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.

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:
-UNIX clients
/usr/openv/netbackup/bin/bp.kill_all
/usr/openv/netbackup/bin/bp.start_all

-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, restart 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.

Attachments:

NB_Appliance_N_2.7.3-1.x86_64-tar-split.1of3   MD5:e4729ecf85117cea8ff12352ac433ca7   SHA1:3f8124ab5775a9f592296ce770c36115ce578e3f

NB_Appliance_N_2.7.3-1.x86_64-tar-split.2of3   MD5:db1d60d441a57c885966e22f3edd39d7   SHA1:ce6a3ebed27f6a040871995a6e438c1488ea03c5

NB_Appliance_N_2.7.3-1.x86_64-tar-split.3of3   MD5:3705bba72021f2435dfc9852d9268178   SHA1:d35d898373b9cb6e78959d7405babc6509015b37

SYMC_NBAPP_addon_nbclient_HP-UX-IA64-7.7.3-0044.x86_64.rpm   MD5:8123d745297ebaa9f3e251a1bd179a0c

SYMC_NBAPP_addon_nbclient_INTEL-7.7.3-0044.x86_64.rpm   MD5:ffd5af8bb1b41bd49b920612e649bb48

SYMC_NBAPP_addon_nbclient_Linux-7.7.3-0044.x86_64.rpm   MD5:2158e2a038a96f320df09bb7994ebb00

SYMC_NBAPP_addon_nbclient_MACINTOSH-7.7.3-0044.x86_64.rpm   MD5:52642d7546281fa308aa359339ee5d1a

SYMC_NBAPP_addon_nbclient_RS6000-7.7.3-0044.x86_64.rpm   MD5:eb18170c42450d7c9ee796a79990948c

SYMC_NBAPP_addon_nbclient_Solaris-7.7.3-0044.x86_64.rpm   MD5:ca70fd83a5b684966dc02971eed8d0fe

SYMC_NBAPP_addon_nbwin-7.7.3-0044.x86_64.rpm   MD5:94a5988044f97d82d3b2603b828d6d5d
 

Was this content helpful?