NetBackup Appliance Upgrade Guide - 3.1
NetBackup Appliance Upgrade Guide - 3.1
Release 3.1
Legal Notice
Copyright © 2017 Veritas Technologies LLC. All rights reserved.
Veritas, the Veritas Logo, and NetBackup are trademarks or registered trademarks of Veritas
Technologies LLC or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.
This product may contain third party software for which Veritas is required to provide attribution
to the third party (“Third Party Programs”). Some of the Third Party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the third party legal notices document accompanying this
Veritas product or available at:
https://www.veritas.com/about/legal/license-agreements
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.
Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:
https://www.veritas.com/support
You can manage your Veritas account information at the following URL:
https://my.veritas.com
If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:
Japan [email protected]
Documentation
The latest documentation is available on the Veritas website:
https://sort.veritas.com/documents
Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:
You can also see documentation information or ask a question on the Veritas community site:
http://www.veritas.com/community/
https://sort.veritas.com/data/support/SORT_Data_Sheet.pdf
Contents
Index .................................................................................................................... 36
Chapter 1
Introduction
This chapter includes the following topics:
■ About upgrades to NetBackup appliance software version 3.1 and the Red Hat
Enterprise Linux operating system
Note: The NetBackup 5200 Appliance does not support upgrade to versions 2.7.1
and later, due to Intel components that are not supported by RHEL version 6.6 or
later.
Note: Appliance upgrades to software version 3.1 and later are not supported from
the NetBackup Appliance Web Console. To upgrade to version 3.1, use the IPMI
console to log in to the NetBackup Appliance Shell Menu.
This topic covers the following information that you should review before an upgrade
to version 3.1:
Supported upgrade paths
Preflight check before the upgrade
Introduction 7
About upgrades to NetBackup appliance software version 3.1 and the Red Hat Enterprise Linux operating
system
Note: For appliances with versions earlier than 2.6.1, refer to the following
document for upgrade instructions: NetBackup Appliance Upgrade Guide -
Software Releases through 2.6.1.2 - SUSE Linux Enterprise Server (SLES)
Operating System. Then use this document to upgrade to version 3.1.
Note: Upgrades to version 2.7.1 and later are not supported if you have installed
Teradata binaries on the appliance. The RHEL operating system does not currently
support the use of these binaries. The upgrade cannot proceed if the preflight check
finds Teradata binaries on the appliance.
Note: The preflight upgrade script only identifies those plug-ins that are required
for the upgrade. At the time when version 2.7.1 was released, some third-party
vendors had not yet completed development of their RHEL equivalent plug-ins.
Make sure to check those vendor websites periodically for any additional plug-ins
that you may need.
■ The appliance reboots four times during the upgrade progress. The following
describes what takes place at each reboot:
Introduction 9
About upgrades to NetBackup appliance software version 3.1 and the Red Hat Enterprise Linux operating
system
■ First reboot - installs the Red Hat Enterprise Linux (RHEL) operating system.
■ Second reboot - initializes the appliance using the new RHEL operating
system.
■ Third reboot - restores the appliance configuration.
■ Fourth reboot - initializes the restored appliance configuration with the RHEL
operating system.
After the first reboot, the NetBackup Appliance Web Console and any
SSH-based connections to the server are unavailable until all reboots have
completed. This condition may last 2 hours or more, depending on the
complexity of the appliance configuration. Do not attempt to manually 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.
After the third reboot occurs, the Appliance Install Manager (AIM) window
appears and shows the upgrade progress.
See “About the Appliance Install Manager” on page 10.
Note: If you select Attempt again and the self-test still fails, the upgrade pauses
again and prompts with the same options.
■ For upgrades from 2.6.1 or 2.6.1.x to 2.7.x or 3.0, the Symantec Critical System
Protection (SCSP) feature is updated to version 6.5 and renamed as Symantec
Data Center Security (SDCS). For all upgrades to 3.1 and later, the SDCS
console and server are no longer included with NetBackup appliance software
upgrade packages.
For more information, refer to the following topic:
See “Post upgrade tasks for 3.1 upgrades” on page 33.
2.7.3 7.7.3
3.0 8.0
3.1 8.1
Upgrade guidelines
Review the following guidelines before you begin the upgrade:
■ Make sure that your appliance environment currently uses software version
2.6.1, 2.6.1.1, 2.6.1.2, 2.7.1, 2.7.2, 2.7.3 or 3.0. Only these versions support a
direct upgrade to version 3.1.
■ Always perform a full disaster recovery (DR) backup before an upgrade.
■ To make sure that there is enough space for the upgrade, delete all previously
downloaded release updates, client packages, and client add-ons from the
appliance before the upgrade. As a best practice, always remove downloaded
packages after all appliances and clients have been upgraded. If the appliance
Upgrade planning 14
Guidelines and best practices for upgrading NetBackup appliances
that you want to upgrade has ever had appliance version 2.6.0.1 installed, it
requires a different method for client package removal.
See “Pre-upgrade tasks for appliance upgrades” on page 16.
■ Follow the same upgrade order for appliances as for traditional NetBackup
upgrades. Always begin by updating the master server appliance, then upgrade
all media server appliances.
■ If you have multiple media servers to upgrade, you must perform the upgrade
process on each individual media server.
■ If a traditional NetBackup master server is used with a media server appliance,
that master server must have the same NetBackup version or later as the media
server appliance. For example, before you upgrade a media server appliance
with NetBackup appliance version 3.1, first upgrade the NetBackup on the master
server to version 8.1.
See “About corresponding NetBackup software versions ” on page 10.
■ Make sure that the NetBackup master server is active and running throughout
the duration of an appliance media server upgrade. In addition, make sure that
the NetBackup processes are started or running on both the master server and
the media server.
Note: Only NetBackup services should be active during an upgrade. All jobs
must be stopped, suspended, or prevented from running during an upgrade.
See “Pre-upgrade tasks for appliance upgrades” on page 16.
Note: This command performs a backup and restore test to the /tmp
directory. If the /tmp directory for the appliance you are upgrading is on the
NetBackup exclude list, you must remove it from that list before you run the
self-test command. Otherwise, the self-test fails.
Note: As a best practice, always remove downloaded packages after all appliances
and clients have been upgraded.
The following table describes the package removal methods for appliances that
never had version 2.6.0.1 installed. For appliances that had version 2.6.0.1 installed,
refer to the information that appears below the table.
Pre-upgrade tasks 18
Pre-upgrade tasks for appliance upgrades
■ Open a web browser or an SSH session to the Veritas appliance software update
release page.
■ Download and install any later version of the client packages onto the appliance.
■ Delete the newly installed client packages from the NetBackup Appliance Shell
Menu. This action also deletes the 2.6.0.1 client packages.
Note: The client packages cannot be deleted from the NetBackup Appliance
Web Console.
http://www.sepaton.com
https://www.veritas.com/product/backup-and-recovery/netbackup-appliances?themeid=nbu-appliance
If you have other third-party plug-ins that you use, those must also be replaced
with the appropriate RHEL versions. See the appropriate vendor website for
details.
■ Open the following share from the NetBackup Appliance Shell Menu:
Manage > OpenStorage > Share > Open.
This command opens the /inst/plugin/incoming share for NFS and the
\incoming_plugins share for Windows. Copy the required plug-ins to these
locations.
■ Close the share as follows:
Manage > OpenStorage > Share > Close.
Note: For upgrades from 2.6.1 or 2.6.1.x, after the RHEL plug-in packages have
been copied into the share and the share has been closed, do not run the Manage
> OpenStorage > List Available command. The current 2.6.x SUSE
appliance code flags the RHEL plug-in packages as invalid because the package
naming conventions are different between SUSE and Red Hat environments.
Since the appliance is still running on SLES, running the List Available
command removes the RHEL plug-in packages from the share which prevents
the upgrade.
Note: An earlier disk drive firmware version does not prevent the software upgrade
from proceeding. If you do not update the disk drive firmware before the appliance
software upgrade, Veritas recommends that you do so immediately afterward.
For complete details about updating the disk drive firmware, refer to following tech
notes:
■ NetBackup appliance models 5230 and 5330 with software versions 2.5 - 2.5.4
https://www.veritas.com/support/en_US/article.000108370
■ NetBackup appliance models 5230 and 5330 with software versions 2.6.0.1 -
2.6.1.2
https://www.veritas.com/support/en_US/article.000108372
Chapter 4
Performing the upgrade
This chapter includes the following topics:
■ If the table does not contain a software update that you want to install,
proceed to the next step.
4 In the Online Software Updates table on the page, select a software update
and click Download.
The Download Progress column shows the download status. After the
download has completed successfully, the software update appears in the
Available Software Updates column of the Downloaded Software Updates
table.
Note: Starting with appliance software version 3.1, the web console no longer
supports the installation of upgrade or EEB packages. After you have downloaded
these packages from the web console, you must perform the installation from the
NetBackup Appliance Shell Menu.
4 To verify that the rpm has downloaded successfully, enter the following
command:
Main_Menu > Manage > Software > List Downloaded
Note: For the 3.1 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. This procedure includes links to access all of these items.
Performing the upgrade 25
Methods for downloading appliance software release updates
Note: If downloading the software updates directly to the appliance fails, use this
method to download the appliance software release update or client package onto
the appliance.
Perform this method from a computer that is connected to the appliance and that
also has Internet access. Internet access is needed to download the files or
packages from the Veritas Support website to the appliance.
To download software release updates or client packages to the appliance
using a CIFS or an NFS client 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
4 This step describes downloading the upgrade package files, the client and
add-on packages, and where to find the MD5 and SHA1 checksums.
■ Release updates
Click on each of the following links to download the split tar server files from
the Veritas SORT website:
http://sort.veritas.com/public/appliance/nba/patches/3.1/NB_Appliance_N_3.1-1.x86_64-tar-split.1of3
http://sort.veritas.com/public/appliance/nba/patches/3.1/NB_Appliance_N_3.1-1.x86_64-tar-split.2of3
http://sort.veritas.com/public/appliance/nba/patches/3.1/NB_Appliance_N_3.1-1.x86_64-tar-split.3of3
■ Client packages
Click on any of the following links to download the specific client or add-on
package from the Veritas SORT website:
http:/sort.veritas.com/public/appliance/nba/patches/3.1/SYMC_NBAPP_addon_nbclient_HP-UX-IA64-8.1-0049.x86_64.rpm
http://sort.veritas.com/public/appliance/nba/patches/3.1/SYMC_NBAPP_addon_nbclient_Linux-8.1-0049.x86_64.rpm
http:/sort.veritas.com/public/appliance/nba/patches/3.1/SYMC_NBAPP_addon_nbclient_RS6000-8.1-0049.x86_64.rpm
http:/sort.veritas.com/public/appliance/nba/patches/3.1/SYMC_NBAPP_addon_nbclient_Solaris-8.1-0049.x86_64.rpm
http://sort.veritas.com/public/appliance/nba/patches/3.1/SYMC_NBAPP_addon_nbwin-8.1-0049.x86_64.rpm
Performing the upgrade 26
Methods for downloading appliance software release updates
5 Use the following commands to join (and extract) the release update .rpm files:
■ For 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
release number and <version> is the posted version number.
■ update.rpm.md5_checksum
■ update.rpm.sha1_checksum
■ For 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-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>".
■ update.rpm.md5_checksum
■ update.rpm.sha1_checksum
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.
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 package .rpm
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
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.
Note: For upgrades from 2.6.1 or 2.6.1.x, the release update or the client
package cannot be verified and moved unless the Symantec Critical System
Protection (SCSP) scanning is complete.
For upgrades from 2.7.1 or later, the release update or the client package
cannot be verified and moved unless the Symantec Data Center Security
(SDCS) scanning is complete.
Performing the upgrade 28
Installing a NetBackup appliance software update using the NetBackup Appliance Shell Menu
■ List Version
■ 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.
See “Downloading software updates to a NetBackup appliance using the NetBackup
Appliance Web Console” on page 22.
Note: Veritas recommends that you log in using the shell menu from the IPMI
console instead of an SSH session. The IPMI console is also known as the
Veritas Remote Manager interface. For details about how to access and use
the Veritas Remote Manager, refer to the following document: NetBackup
Appliance Hardware Installation Guide.
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.
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:
See “Pre-upgrade tasks for appliance upgrades” on page 16.
5 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:
■ 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:
>> Enter token:
Note: If the appliance is ever factory reset or re-imaged after it has been
upgraded to version 3.1, a reissue token is required for the next upgrade.
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.
7 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.
Performing the upgrade 31
Installing a NetBackup appliance software update using the NetBackup Appliance Shell Menu
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.
■ 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 Veritas 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 on 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.
8 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:
/log/selftest_report_<appliance_serial>_<timedate>.txt
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
■ 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.
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.
Chapter 5
Post upgrade tasks
This chapter includes the following topics:
D T
disk drive firmware 20 troubleshoot upgrade issues 35
download directly
appliance server or client package 23 U
download methods update disk drive firmware 20
release updates 22 upgrade
download software updates pre-upgrade tasks 16
from NetBackup Appliance Web Console 22 version 3.1 with RHEL operating system 6
using client share 24 upgrade guidelines 13
upgrade time estimation 12
G upgrades
guidelines and best practices supported upgrade paths 7
appliance upgrades 12
V
I version 2.7.x upgrades
install update from NetBackup Appliance Shell Menu RHEL third-party plugins 8
version 3.1 28 version 3.1
install update from NetBackup Appliance Shell
Menu 28
P version 3.1 upgrades
post upgrade tasks RHEL operating system 6
SDCS mode 33
pre-upgrade tasks
delete previously downloaded packages 17
deleting version 2.6.0.1 client packages 18
obtain RHEL third-party plug-ins 19
stop backups and run self-test 16