Please contact your Business Critical Services representative or call Veritas Support to access NetBackup Appliance 3.x/3.x.x upgrade files and receive important upgrade instructions.
Note: NetBackup Appliance release 3.1 has been updated as of November 8, 2017. This updated release helps to ensure a successful upgrade and it also includes an automatic EEB installation that resolves a kernel panic problem. If you have already upgraded successfully to appliance release 3.1 before November 8, 2017, you do not need to upgrade again. To resolve an existing kernel panic problem or to prevent one in the future, refer to the following article to obtain an EEB to fix the issue:
NetBackup appliance software version supports direct upgrades for appliance models 5220, 5230, 5240, and 5330 that currently use software versions 2.6.1, 126.96.36.199, 188.8.131.52, 2.7.1, 2.7.2, 2.7.3, or 3.0.
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, 184.108.40.206, or 220.127.116.11, certain pre-upgrade tasks must be performed to help ensure a successful upgrade. For complete details, see the NetBackup Appliance Upgrade Guide - Red Hat Enterprise Linux (RHEL) Operating System.
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.
Note: The 3.1 release update packages and the add-on packages are not attached to this file. The following procedure includes links to the Veritas SORT website where the packages are located.
TABLE OF CONTENTS
- Product Dependencies
- Downloading and Installation Instructions
- For appliances that are configured as a media server, this upgrade requires a NetBackup Appliance 3.1 master server appliance or a traditional NetBackup 8.1 master server. Master servers must be upgraded before media servers.
- This release supports a direct upgrade from versions 2.6.1, 18.104.22.168, 22.214.171.124, 2.7.1, 2.7.2, 2.7.3, or 3.0. For complete details about upgrades to version 3.1, refer to the NetBackup Appliance Upgrade Guide - Red Hat Enterprise Linux (RHEL) Operating System .
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.
Note: Software version 3.1 provides a new Appliance Management Console that lets you manage multiple 3.1 NetBackup appliances. If you want to upgrade appliances with versions 2.7.3 or 3.0 from the Appliance Management Console, you must first apply the following EEBs on those appliances:
- For appliances with version 2.7.3:
- For appliances with version 3.0:
Installing the applicable EEBs on NetBackup appliance versions 2.7.3 and 3.0 enables you to add these appliances as agents to the Appliance Management Console. See the following link for instructions on how to add the appliances to an Appliance Management Console:
Once the 2.7.3 and 3.0 appliances are added, they can be upgraded from the Appliance Management Console. See the Appliance Management Guide for more information.
Note: The Appliance Management Console lets you upgrade and install an EEB on multiple 3.1 NetBackup appliances. However, installing an EEB on the 2.7.3 and 3.0 appliances from the Appliance Management Console is not supported.
Downloading and Installation Instructions
Note: For this release, the server, client, and add-on packages are located on the Veritas SORT website, along with a text file that contains the MD5 and SHA1 checksums. The following procedure includes links to access all of these items.
The following procedure describes how to download and install the NetBackup appliance version 3.1 release update. Instructions are included for the server packages only. For client and add-on packages, use the following link for downloading and installation instructions:
Manually downloading NetBackup appliance server packages
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 appliance software release updates 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. Open an NFS or a CIFS share by entering the following command:
Main_Menu > Manage > Software > Share Open
3. Map or mount the appliance share directory as follows:
Map the following appliance CIFS share on your computer:
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 downloading the upgrade package files and where to find the MD5 and SHA1 checksums.
- Click on each of the following links to download the split tar server files from the Veritas SORT website:
- Click on the following link to a text file on the Veritas SORT website that contains the MD5 and SHA1 checksums:
Verify that the downloaded MD5 or SHA1 checksums match those in the text file on the Veritas SORT website.
5. Use one of the following commands to join (and extract) the release update .rpm files:
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-version > is the software release number, such as 3.1, and the version number of the software release, such as -1 .
Use Windows WinRAR utilities to uncompress the NB_Appliance_N_< release-version>.tar file. The resulting files are as follows:
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-version > is the software release number, such as 3.1, and the version number of the software release, such as -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:
6. For UNIX systems, run one of the following commands to compute the checksum value for the .rpm file:
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 .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 .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
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.
11. To install the software release update, run the following command:
Main_Menu > Manage > Software > Install SYMC_NBAPP_update-< release-version>.x86_64.rpm
12. Monitor the preflight check and watch for any Check failed messages.
After the preflight check has finished, 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. 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: NetBackup Appliance Upgrade Guide for details.
13. After all preflight check items have passed, you may need to trust the CA certificate and the host ID-based certificate to start the upgrade process. To trust and deploy the CA certificates, do the following:
- Verify the CA certificate detail and enter yes to trust the CA certificate, as follows:
CA Certificate Details:
Subject Name : /CN=nbatd/OUemail@example.com/O=vx
Start Date : Jul 14 12:59:18 2017 GMT
Expiry Date : Jul 09 14:14:18 2037 GMT
SHA1 Fingerprint : 31:E9:97:2E:50:11:51:7C:D6:25:7F:32:86:3D:
>> Do you want to trust the CA certificate? [yes, no](yes)
- If the security level of the master server is Very High, you must manually enter an authorization token to deploy the host ID-based certificate on the appliance, as follows:
- If the security level of the master server is High or Medium, the authentication token is not required. The host ID-based certificate is automatically deployed onto the appliance.
14. To check the upgrade status before the AIM window appears, enter the following command:
The system reboots 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 two hours or more, depending on the complexity of the appliance configuration. It is important that you do not attempt to manually reboot the appliance during this time. You can use the Veritas Remote Management interface (IPMI) to view the system 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.
After the third reboot occurs, the AIM window appears automatically and shows the upgrade progress and the estimated remaining time.
Note: Do not close the AIM window until after the upgrade has completed.
15. If problems are detected during the post-upgrade self-test, the AIM window shows the upgrade status as Paused. Other SSH sessions and email notifications also indicate this status.
Note: If a Paused status occurs, the AIM window on the IPMI console becomes locked and does not respond to keyboard input. Before you can clear the Paused status, you must unlock the AIM window as described below.
To clear the Paused status, try the following tasks:
- Unlock the AIM window on the IPMI console as follows:
- Press the Enter key several times until the login prompt appears.
- Enter the user account name and the password to log in to the IPMI console again. After logging in, the AIM window reappears and should respond to keyboard input.
- Continue with the following tasks to clear the Paused status.
- Press the V key to switch to the Verbose view to see the logs. If there are any Unique Message Identification (UMI) codes for the errors, search for them on the https://www.veritas.com/support website to get more detailed information.
- Try to fix the problem that the AIM window reports. If you need to use the shell menu, log in to the NetBackup Appliance Shell Menu through an SSH session. When the AIM window appears, press the S key to close it.
- Go back to the AIM window on the IPMI console. If you tried fixing the problem, press the A key to attempt the self-test again. If you cannot fix the problem, contact Veritas Technical Support or press the R key to roll back the appliance to the previous software version.
16. After the upgrade has completed, the AIM window shows a summary of the upgrade results. 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:
If SMTP is configured, an email notification that contains the self-test result is sent.
17. 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:
- Log on to this appliance as one of the listed NetBackup users.
- Run the following command to rescan the FC ports:
- If any SAN clients still do not work, run the following commands on each of those clients in the order as shown:
On Windows clients:
- 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 nbftconfigrescanallclients command again.
- If any SAN clients still do not work, restart those clients.
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):