NetBackup105 UpgradeGuide
NetBackup105 UpgradeGuide
Guide
Release 10.5
NetBackup™ Upgrade Guide
Last updated: 2024-09-17
Legal Notice
Copyright © 2024 Veritas Technologies LLC. All rights reserved.
Veritas, the Veritas Logo, Veritas Alta, 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.
http://www.veritas.com
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
Make sure that you have the current version of the documentation. Each document displays
the date of the last update on page 2. 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
NetBackup primary server web server user and group creation ............ 137
NetBackup database user ............................................................ 139
Generate a certificate on the inactive nodes of a clustered primary
server ................................................................................. 140
About the NetBackup Java Runtime Environment .............................. 141
Add or Remove Java GUI and JRE after upgrade .............................. 144
About the NetBackup web user interface ......................................... 145
About the NetBackup answer file ................................................... 146
About pushing client software from a primary server to clients .............. 173
Installing client type software on a primary server ........................ 174
About the NetBackup IT Analytics Data Collector .............................. 175
Manually install or uninstall NetBackup IT Analytics Data Collector
binaries .............................................................................. 176
Manually configure the NetBackup IT Analytics Data Collector ............. 177
Manually upgrading the NetBackup IT Analytics Data Collector ............ 181
Persistent Java Virtual Machine options .......................................... 182
About RBAC bootstrapping ........................................................... 182
About NetBackup software availability ............................................. 184
Additional post-upgrade steps for NetApp clusters ............................ 184
Contents 7
Interactive See “Upgrading Linux server See “Upgrading NetBackup Yes. See the information
software to NetBackup 10.5” media servers to NetBackup about primary servers.
on page 62. 10.5” on page 86.
See “About VxUpdate”
See “About VxUpdate” on page 116.
on page 116.
Silent or native See “Silently upgrading See “Silently upgrading See “Upgrade of the UNIX
NetBackup primary server NetBackup media server and Linux client binaries with
software on Linux” software on Linux” native installers”
on page 70. on page 89. on page 102.
Push or remote Upgrade: No See “About VxUpdate” See “Upgrading clients after
on page 116. servers are upgraded”
EEB: Push upgrade of EEBs
on page 203.
may work through 3rd party
deployment tools. You can Chef and SCCM templates
also use the Chef and
https://sort.veritas.com/utility/
SCCM templates provided
netbackup/deployment
by Veritas.
See “About VxUpdate”
on page 116.
Interactive See “Performing local, See “Upgrading NetBackup Yes. See the information
remote, or clustered server media servers to NetBackup about primary servers.
upgrades on Windows 10.5” on page 86.
See “About VxUpdate”
systems” on page 47.
See “About VxUpdate” on page 116.
on page 116.
Silent See “Performing silent See “Performing silent Yes. See the information
upgrades on Windows upgrades on Windows about primary servers.
systems” on page 58. systems” on page 58.
See “About VxUpdate”
See “About VxUpdate” on page 116.
on page 116.
Introduction 11
About changes in NetBackup 10.5
Push or remote Upgrade: See “Performing See “Upgrading NetBackup Yes. See the information
local, remote, or clustered media servers to NetBackup about primary servers.
server upgrades on 10.5” on page 86.
Chef and SCCM templates
Windows systems”
See “About VxUpdate”
on page 47. https://sort.veritas.com/utility/
on page 116.
netbackup/deployment
EEB: Push upgrade of EEBs
may work through 3rd party See “About VxUpdate”
deployment tools. You can on page 116.
also use the Chef and
SCCM templates provided
by Veritas.
About VxUpdate
VxUpdate provides a policy-based and on demand upgrade tool for media servers
and clients. The policy format provides a simplified tool for media server and client
upgrades. The on demand ability provides immediate upgrades as needed.
The VxUpdate configuration is in a familiar policy-based format, similar to a backup
policy. You can use the deployment policies to automate the installation of
emergency engineering binaries, as provided by Veritas. The deployment policy
lets you configure and run deployment activities on a schedule or enable the client
host owners to upgrade on demand. Veritas recommends use of VxUpdate for push
or remote upgrades where possible.
To continue to use the Instant Access or malware scans of VMware images, use
the libguestfs.rpm and python3-libguestfs.rpm packages. The NetBackup
upgrade script automatically removes VRTSpddei if it detects that these two new
RPMs are present. Otherwise, the upgrade script notifies the user that there are
manual steps to install the new RPMs and remove VRTSpddei.
UI immediately after upgrade, indicating the number of days remaining before the
temporary license expires.
More information about license files is available.
https://www.veritas.com/support/en_US/article.100058779
that the upgrade requires approximately twice the space of the current NetBackup
database for the conversion.
Veritas recommends that you run the database precheck tool to identify any potential
data issues before you upgrade NetBackup. See
https://www.veritas.com/support/en_US/article.100055151 for instructions about
how to use the precheck tool. Veritas also recommends that you defragment the
NetBackup database before upgrade to improve the overall conversion experience.
See the NetBackup Administrator's Guide, Volume I for additional information on
the Reorganize option to defragment the database.
Caution: Usage Insights is compatible with Google Chrome and Mozilla Firefox.
Veritas does not recommend using Microsoft Edge or Microsoft Internet Explorer,
as they do not render all information correctly.
https://www.veritas.com/support/
en_US/article.100058779
Before you begin an upgrade, Veritas recommends that you review the NetBackup
Release Notes document that is included with your media kit or the electronic
product image files. This document describes important changes in NetBackup
10.5 that you should be familiar with before you upgrade.
Caution: To help ensure a successful upgrade to NetBackup 10.5, you should visit
the SORT page and the NetBackup Upgrade Portal and for complete upgrade
details:
SORT page:
https://sort.veritas.com/netbackup
See “About Veritas Services and Operations Readiness Tools” on page 29.
NetBackup Upgrade Portal:
https://www.veritas.com/support/en_US/article.100032801
Planning for an upgrade 19
General upgrade planning information
Note: It is recommended that you save the details of the user account that you use
for the NetBackup Web Services. A primary server recovery requires the same
NetBackup Web Services user account and credentials that were used when the
NetBackup catalog was backed up.
Caution: If the NetBackup PBX is running in secure mode, please add the web
service user as authorized user in PBX. More information about determining PBX
mode and how to correctly add users is available.
http://www.veritas.com/docs/000115774
For example:
NB_KEYSIZE = 4096
The NB_KEYSIZE can only have the following values: 2048, 3072, 4096, and 8192.
Note: If the FIPS mode is enabled on the primary server, you can only specify 2048
bits or 3072 bits as a value for the NB_KEYSIZE environment variable.
Caution: You should carefully choose the key size for your environment. Choosing
a large key size may reduce performance. You should consider all factors to
determine the correct key size for your environment.
For more information about CA migration and certificate key sizes, see the
NetBackup Security and Encryption Guide.
Table 2-2 shows the overview of the upgrade procedure.
1 Review operating system requirements and confirm See “Upgrade requirements for UNIX and Linux”
the computer meets all requirements. on page 191.
2 Confirm that the web server user account and group More information is available:
account are created and enabled.
See “NetBackup primary server web server user and
group creation” on page 137.
3 Begin the upgrade process See “About primary server upgrades” on page 41.
You can change log file permissions to the less restrictive setting by changing
ALLOW_WORLD_READABLE_LOGS to YES. If you want to retain the less restrictive log
permissions during the NetBackup 10.5 upgrade, set
ALLOW_WORLD_READABLE_LOGS=YES with the nbsetconfig command before you
upgrade.
To again restrict the legacy log permissions, set ALLOW_WORLD_READABLE_LOGS=NO
with nbsetconfig.
See the NetBackup Commands Reference Guide for assistance with the
nbsetconfig command.
See the NetBackup Logging Reference Guide for additional information about the
ALLOW_WORLD_READABLE_LOGS value.
See the NetBackup Logging Reference Guide for additional information about the
ALLOW_WORLD_READABLE_LOGS value.
is not migrated. Any previously added Resiliency Domains are no longer present
on the Resiliency tab in the NetBackup web interface.
You can reconfigure and rediscover the Resiliency information on the Resiliency
tab by performing the steps that are shown in the referenced tech note. The
Resiliency tab contains configuration information about the Veritas Resiliency
Platform (VRP) and all the data pertaining to that resiliency domain, including
managed and unmanaged assets.
You must reconfigure after the upgrade completes to rediscover the resiliency
domain data. Refer to the referenced tech note for additional information on how
to reconfigure VRP after upgrading NetBackup to 10.0.
https://www.veritas.com/support/en_US/article.100052464
The information that is not migrated as a part of the NetBackup 10.0 upgrade is
stored in these files:
■ vrp-h2-store.mv.db
■ messages-h2-store.mv.db
■ notifications-h2-store.mv.db
These files are preserved on the primary server in the following directories. These
files remain in the specified location unless you remove them. You cannot use these
files in a NetBackup to 10.0 or later environment:
■ Windows files:
install_path\NetBackup\var\global\wmc\h2stores\vrp-h2-store.mv.db
install_path\NetBackup\var\global\wmc\h2stores\messages\
messages-h2-store.mv.db
install_path\NetBackup\var\global\wmc\h2stores\notifications\
notifications-h2-store.mv.db
■ Linux files:
/usr/openv/var/global/wmc/h2stores/vrp-h2-store.mv.db
/usr/openv/var/global/wmc/h2stores/messages/
messages-h2-store.mv.db
/usr/openv/var/global/wmc/h2stores/notifications/
notifications-h2-store.mv.db
If the primary server performs catalog backups to a separate media server, that
media server must use the same version of NetBackup as the primary server. Since
the NetBackup catalog resides on the primary server, the primary server is
considered to be the client for a catalog backup.
As such, the media server must have the same version of NetBackup as the primary
server.
Failure to use the same version of NetBackup on the media server results in
improperly protected catalog data.
More information on mixed version support is available.
See “About compatibility between NetBackup versions” on page 191.
initbpdbm.version
/usr/openv/volmgr/help /usr/openv/netbackup/
bin/goodies.version
For Windows
Table 2-4 Protected paths and files for Windows
directory.
Example:
Planning for an upgrade 28
General upgrade planning information
install_path\NetBackup\bin\goodies\help_script.cmd install_path\NetBackup\bin\
install_path\NetBackup\bin\goodies\available_media.cmd goodies.release
install_path\NetBackup\bin\goodies\check_coverage.cmd directory.
install_path\NetBackup\bin\goodies\bpstart_notify install_path\NetBackup\bin\
goodies.version\netbackup.adm
install_path\NetBackup\bin\goodies\bpend_notify
Table 2-5
Procedure Details
Create a Veritas Account on the SORT See “To create a Veritas Account on the
webpage SORT page” on page 31.
Procedure Details
Review the future platform and feature plans. See “To review future platform changes and
feature plans” on page 33.
Review the hot fix and emergency See “To review hot fix and emergency
engineering binary release auditor engineering binary information” on page 34.
information.
CAPTCHA text Enter the displayed CAPTCHA text. If necessary, refresh the
image.
4 Click Submit.
5 When you receive your login information, you can log into SORT and begin
uploading your customized information.
To create a system-specific installation report for Windows
1 Go to the SORT website:
https://sort.veritas.com/netbackup
2 In the Installation and Upgrade section, select Installation and Upgrade
custom reports by SORT data collectors.
3 Select the Data Collectors tab
Planning for an upgrade 32
About upgrade tools
4 Select the radio button for Graphical user interface and download the correct
data collector for your platform.
The data collector is OS-specific. To collect information about Windows
computers, you need the Windows data collector. To collect information about
UNIX or Linux computers, you need the UNIX or Linux data collector.
5 Launch the data collector after it finishes downloading.
6 On the Welcome screen, select NetBackup from the product family section
and click Next.
7 On the System Selection screen, add all computers you want analyzed. Click
Browse to see a list of computers you can add to the analysis. Veritas
recommends starting the tool with an administrator or a root account.
8 When all systems are selected, review the System names section and click
Next.
9 In the Validation Options screen, under Validation options, select the version
to which you plan to upgrade.
10 Click Next to continue
11 The utility performs the requested checks and displays the results. You can
upload the report to My SORT, print the results, or save them. Veritas
recommends that you upload the results to the My SORT website for ease of
centralized analysis. Click Upload and enter your My SORT login information
to upload the data to My SORT.
12 When you are finished, click Finish to close the utility.
To create a system-specific installation report for UNIX or Linux
1 Go to the SORT website:
https://sort.veritas.com/netbackup
2 In the Installation and Upgrade section, select Installation and Upgrade
custom reports by SORT data collectors.
3 Select the Data Collector tab.
4 Download the appropriate data collector for your platform.
The data collector is OS-specific. To collect information about Windows
computers, you need the Windows data collector. To collect information about
UNIX or Linux computers, you need the UNIX or Linux data collector.
5 Change to directory that contains downloaded utility.
Planning for an upgrade 33
About upgrade tools
6 Run ./sortdc
The utility performs checks to confirm the latest version of the utility is installed.
In addition, the utility checks to see it has the latest data. The utility then lists
the location of the log file for this session.
7 If requested, press Enter to continue.
8 Select the NetBackup Family at the Main Menu.
9 Select Installation/Upgrade report when prompted What task do you want
to accomplish?
You can select multiple options by separating your response with commas.
10 Specify the system or systems you want included in the report.
If you previously ran a report on the specified system, you may be prompted
to run the report again. Select Yes to re-run the report.
The utility again lists the location of the log files for the session.
The progress of the utility is displayed to the screen.
11 Specify NetBackup when prompted for the product you want installation or
upgrade reports.
12 Enter the number that corresponds to the version of NetBackup you want to
install.
The utility again lists the location of the log files for the session.
The progress of the utility is displayed to the screen.
13 The utility prompts you to upload the report to the SORT website if you want
to review the report online. The online report provides more detailed information
than the text-based on-system report.
14 When your tasks are finished, you can exit the utility. You have the option to
provide feedback on the tool, which Veritas uses to make improvements to the
tool.
To review future platform changes and feature plans
1 In your web browser, navigate to:
https://sort.veritas.com/netbackup
2 Find and select the NetBackup Future Platform and Feature Plans widget.
3 Select Display Information.
4 Review the information provided
5 Optional - sign in to create notification - Click Sign in and create notification.
Planning for an upgrade 34
About upgrade tools
Hot fix of EEB Shows the hot fix or EEB number that was entered on the
Identifier previous screen.
updates the checker with the latest version when the installation or the upgrade
starts.
One of the tests that is performed is a comparison of the locally installed Emergency
Engineering Binary (EEB) updates with the fixes included with the version of
NetBackup being installed. If any of the preinstall tests fail, a message appears to
indicate what type of action is required.
Some test failures are considered minor and let you continue with the installation
or the upgrade. Critical test failures prevent the installation or the upgrade from
happening. The output informs you that other action must be taken before you can
proceed safely with the installation or the upgrade.
The preinstall check results are stored in the following locations:
■ Linux
In the installation trace file in the following path:
/usr/openv/tmp
■ Windows
In the following directory:
%ALLUSERSPROFILE%\Veritas\NetBackup\InstallSummary\
■ IBMzSeriesRedHat: 4.18.0-372
■ Debian: 4.18.0-372
■ IBMpSeriesSuSE: 5.3.18-22
■ IBMzSeriesSuSE: 5.3.18-22
Note: For Linux platforms, the UID must be the same for each local account in a
clustered environment. Be sure that the local accounts are defined consistently on
all cluster nodes.
Installation of the NetBackup primary server fails if any of these requirements are
not met. On Windows, you are asked to provide the password for the user account
as part of the installation process.
About NetBackup 10.5 support for Fibre Transport Media Server with
RHEL 7.5 and later
If you plan to use Fibre Transport Media Server (FTMS) with RHEL 7.5 and later,
ensure that you upgrade NetBackup to 8.1.2 or later. You can also use a new RHEL
7.5 or later release system that has NetBackup 8.1.2 or later.
Before you upgrade RHEL to 7.5 or later release, complete the following steps:
1 Disable FTMS.
2 Upgrade NetBackup to 8.1.2 or later.
3 Upgrade RHEL to 7.5 or later release and then reconfigure FTMS.
For more information about reconfiguring FTMS, see the NetBackup SAN Client
and Fibre Transport Guide.
Planning for an upgrade 39
Upgrade operational notes and limitations
If the client in the originating domain is NetBackup 10.5 and the primary in the target
domain is 10.1, the BMR information fails to replicate. All other information is
successfully sent, only the BMR information is not replicated. You can restore the
contents of the client, but you cannot use BMR.
More information about this topic is available.
http://www.veritas.com/docs/TECH211267
Upgrade issue with pre-8.1 clients and 8.1 or later media servers
With the NetBackup 8.1 upgrade, the fingerprinting algorithm was upgraded from
MD5 to SHA2 to provide improved protection against security vulnerabilities. Veritas
introduced two conversion methods to convert existing MD5 fingerprint data to
SHA2: rolling conversion and inline conversion. Problems occur under the conditions
shown:
■ Client is pre-8.1 NetBackup.
■ Client uses Client Direct, which performs deduplication at the client.
■ Client is backed up by a NetBackup 8.1 or later media server.
Under these conditions, the fingerprint conversion happens inline. As a result,
backup performance is negatively effected and the CPU processing load on the
media server increases. The media server has to rehash the MD5 information and
create a SHA2 fingerprint.
To prevent this issue:
■ For pre-8.1 clients, change their backup to use media server deduplication
(MSDP) with a media server that is at NetBackup 8.1 or later. This action avoids
the backup performing the inline conversion.
■ Do not use Client Direct on pre-8.1 clients that are backed up by 8.1 and later
media servers.
Chapter 3
Primary server upgrade
This chapter includes the following topics:
Note: It is recommended that after you install or upgrade NetBackup server software,
you uninstall older versions of the Remote Administration Console (Windows and
Java) present on the host. If the native NetBackup Administration Console for
Windows is present, it is automatically uninstalled when you install or upgrade the
NetBackup server software.
3 Run the database precheck tool to confirm your environment is ready for
conversion to the new NetBackup database. For details about this tool, see:
https://www.veritas.com/support/en_US/article.100055151
4 (Conditional) On Linux, if the NetBackup database files reside on btrfs file
system, move it to a supported file system (such as ext4 or xfs) before you
upgrade. It is not supported to reside the NetBackup database on a btrfs file
system. The database files reside on the primary server in the directories under
/usr/openv/db.
■ For VMware and Red Hat Virtualization (RHV) environments, reduce the
size of the job database before upgrade. Following an upgrade, existing
VMware and RHV jobs are assigned an asset namespace to enable access
control at an asset level. This process may take some time. More information
about this process is available:
See “Reduce the job database size before upgrade” on page 28.
■ For clustered systems only, take the following NetBackup resources offline:
■ Windows Server Failover Clusters (WSFC): Take all of the NetBackup
group resources offline except for the disk, the virtual name, and the
virtual IP address. Refer to the Microsoft Cluster Administration
documentation to determine how to take the NetBackup group resources
offline through the cluster administrator interface.
■ Cluster Server (VCS) clusters: Take the NetBackup resource offline.
Freeze the NetBackup group with the -persist option using the
command shown:
hagrp -freeze NetBackup_service_group -persistent
Refer to the NetBackup Clustered Primary Server Administrator’s Guide
for the commands to take these resources offline.
8 (Conditional) If you plan to change your NetApp cluster to Vserver mode from
node scope mode, create a detailed image report for each filer. You can
generate this report with the bpimagelist command. The example that is
shown is one possible option. Use whatever options are necessary for your
environment.
bpimagelist –client ndmp_host_name
Primary server upgrade 46
Preinstall procedure for upgrading to NetBackup 10.5
Note: It is recommended that you save the details of the user account that you
use for the NetBackup Web Services. A primary server recovery requires the
same NetBackup Web Services user account and credentials that were used
when the NetBackup catalog was backed up.
Note: If the NetBackup PBX is running in secure mode, please add the web
service user as authorized user in PBX. More information about determining
PBX mode and how to correctly add users is available.
http://www.veritas.com/docs/000115774
10 (Conditional) If you have customized the settings for your Tomcat web server,
determine if those settings persist across upgrades. More information is
available:
See “Persistent Java Virtual Machine options” on page 182.
11 Stop any applications on the system that interact with NetBackup. This step
includes any databases or system components being backed up. Failure to
stop these applications may result in unexpected behavior. Observed behavior
includes aborted upgrades and application failures.
For Oracle users, ensure that no backups are running. Stop the RMAN
processes before you install NetBackup. If you use AIX, you should run
/usr/bin/slibclean as the root user after you stop the RMAN processes.
If you cannot stop your Oracle database, a procedure is available that may let
you install NetBackup with the Oracle database active. More information on
this topic is available.
http://www.veritas.com/docs/TECH158276
12 Stop all NetBackup services.
■ On UNIX systems: /usr/openv/netbackup/bin/bp.kill_all
■ On Windows systems: install_path\NetBackup\bin\bpdown -f
Primary server upgrade 47
Performing local, remote, or clustered server upgrades on Windows systems
2 Navigate to the directory where the ESD images (downloaded files) reside and
run Browser.exe to start the NetBackup Installation Wizard.
3 On the initial browser screen (Home), click Install/Upgrade.
4 On the Install/Upgrade screen, click NetBackup Server Software
Install/Upgrade.
5 If you are prompted about the absence of required Visual C++ run-time libraries,
review the information and respond accordingly. More information is available.
See “Windows compiler and security requirements for NetBackup 10.5 and
later upgrade” on page 36.
6 On the Welcome screen, review the content and click Next.
7 (Conditional) If you previously installed NetBackup 10.5 on this host, you see
the Program Maintenance dialog.
Primary server upgrade 48
Performing local, remote, or clustered server upgrades on Windows systems
■ Select Modify to change installation settings for the local host, or to use
the local host as a platform to perform push installation to remote hosts.
■ Select Repair to restore NetBackup 10.5 to its original state on the local
host.
■ Select Remove to remove NetBackup 10.5 from the local host.
Click Next.
10 On the NetBackup Server Role and Licenses screen, provide the following
information:
■ License
Upgrades from versions earlier than NetBackup 8.1.2 only support the
production licenses that are downloaded from the Veritas Entitlement
Management System (VEMS) or the evaluation license. You cannot use
Primary server upgrade 49
Performing local, remote, or clustered server upgrades on Windows systems
Note: For remote upgrades, the license that you enter here gets pushed
to the other nodes. Your license may enable add-on products. If you push
NetBackup to nodes that have an add-on product already installed, your
license works for the add-on product(s).
For remote or for clustered upgrades, the following occurs during the
upgrade process to verify that you have the proper credentials to perform
the upgrade:
■ When you select a clustered system for upgrade, NetBackup determines
if you have proper administrator credentials on all nodes in the cluster.
If you do not have the proper credentials, the system is not added to
the list.
■ If you have the proper credentials, you must enter a valid license to
upgrade that node.
For upgrades from pre-10.3 to 10.3 or later release, if no license is
provided, NetBackup uses in-built temporary production license. More
information is available:
https://www.veritas.com/support/en_US/article.100058779
For upgrade from 10.3 or later releases, if license is either invalid or
expired, the precheck fails for remote or clustered Windows installation.
The NetBackup version on that node remains unchanged and NetBackup
continues to function. For a successful upgrade, you must provide a
valid license.
For push installation to multiple computers in the network, the upgrade
fails at the precheck if the remote computer doesn't have a valid license.
NetBackup on that node is not upgraded but it continues to function.
For clustered primary server, the licenses are stored on the shared disk
that is accessible only to the active node. As such, the license isn't
pushed to the inactive nodes.
■ Select NetBackup Primary Server, browse and add licenses, and then
Next to proceed to upgrade the primary server software. More information
about licenses is available:
https://www.veritas.com/support/en_US/article.100058779
Primary server upgrade 50
Performing local, remote, or clustered server upgrades on Windows systems
Click Next.
■ NetBackup Services
On this screen, provide the following startup account and startup type
information for NetBackup services:
Privileged Account Details Specify either Local System account or Custom account.
By default, the Local System account is selected, so that NetBackup uses the built-in
system account. When this option is selected, the fields below it are disabled.
To specify a different system account:
■ Select Custom account.
■ Enter the account information in the following fields:
Domain
Username
Password
Non-Privileged Account Specify either Same as the Privileged Account specified above or Local Service
Details account.
Using a local service account involves a one-time conversion that may significantly
increase the upgrade time based on your catalog size.
For more information for the non-privileged service user account, refer to:
https://www.veritas.com/docs/100048220
Startup Type This option determines whether NetBackup services start automatically if you need to
restart the NetBackup host. The default is Automatic.
Start job-related NetBackup By default, job-related services are set to start automatically after the upgrade has
services after completion completed.
To prevent job-related services from starting automatically, click on the box to clear
the check mark.
Safe Abort Option This option determines how the upgrade proceeds if a restart is required as part of the
upgrade.
If you select this option and the upgrade process determines that a restart is required,
the upgrade stops. The system is then rolled back to its original state.
If you do not select this option, the upgrade proceeds even if the upgrade process
determines that a restart is required.
Click Next.
13 On the NetBackup Web Services screen, enter the Web Services Password.
Primary server upgrade 52
Performing local, remote, or clustered server upgrades on Windows systems
This password is the password for the NetBackup web services user account.
You must create this account before you install the primary server. More
information is available.
On the NetBackup Web Services screen, specify the account type and the
account details.
Note: You can use the $hostname variable for any of the names in the
certificate store specification. The $hostname variable evaluates at run time
to the name of the local host. This option provides flexibility when you push
NetBackup software to a large number of clients.
Browse Click here to search the network for the hosts where you want to upgrade NetBackup.
■ On the Available Systems dialog box, select the computer to add and click Next.
■ On the Remote Computer Login Credentials dialog box, enter the user name,
the password, and the domain of the account for NetBackup to use on the remote
computers.
■ If you plan to upgrade multiple remote computers, click the box next to Remember
User Name and Password. Selecting this option prevents the need to enter this
information for each remote computer.
When you provide credentials, you select host nodes and add them to the Windows
Destination Systems list. These are the nodes on which you remotely upgrade
NetBackup. Make sure that you select your local host when you select systems to
install.
Each time you choose a system, NetBackup performs a system check. For example,
it verifies the system for a server upgrade that matches the type that you selected,
as follows:
■ NetBackup not installed: Considers the remote to be verified.
■ NetBackup already installed: Compares the upgrade type on that system to the
upgrade type that you request.
■ Invalid combination: Notifies you of the problem and disallows the choice. One
example of an invalid combination is to try to install a Remote Administration
Console on a remote system that is already a primary server.
■ Remote system not a supported platform or level: Notifies you of the problem
and disallows the choice.
The upgrade procedure also verifies that you have proper administrator credentials
on the remote system. If you do not have administrator credentials, the Enter
Network Password screen appears, and prompts you to enter the administrator’s
user name and password.
Click OK and continue selecting destination systems.
This process repeats for each node that you select. You can elect to retain the user
name and password. In that case, you are prompted only when the user name or
password is not valid.
Note the following about the push-install process in a clustered environment:
■ You can upgrade NetBackup on any number of nodes. However, the clustering
service sets the limit for the number of nodes in a cluster, not NetBackup.
■ Language packages and other NetBackup add-on products cannot be upgraded
with the push method. Add-on products must be upgraded on each individual
node in the cluster group. For instructions on how to upgrade these products,
refer to the NetBackup documentation that supports each product.
■ NetBackup pushes to the other nodes only the license you enter at the beginning
of the upgrade. Your license may enable add-on products. If you push NetBackup
to nodes that have an add-on product already installed, your license works for
that product.
■ Click OK.
Primary server upgrade 56
Performing local, remote, or clustered server upgrades on Windows systems
Import Click here to import a text file that contains a list of host names. When you create the
text file, the host names must be defined in the following format:
Domain\ComputerName
Remove To remove a host from the Destination Systems list, select the host and click here.
Change Click here to change the destination for NetBackup file installation on the selected
remote host.
■ Click Next.
16 For cluster upgrades only, on the Cluster Settings screen, review the
information displayed. All information except the Public Network is displayed
for informational purposes and cannot be changed. If you need to change the
public network, select the correct public network from the drop-down.
Warning: You must not select a private network that is assigned to this cluster.
18 On the Ready to Upgrade screen, review the Upgrade Summary that shows
your selections from the previous steps.
If the ECA heath check utility indicates the Cryptographic Service Provider
(CSP) or the Key Storage Provider (KSP) doesn't support the security
descriptors, the upgrade cannot proceed.
This flag indicates that the provider cannot be used when NetBackup services
are run in the local service user account context. Use a provider that supports
security descriptors or use an administrator account to run all NetBackup
services.
For more details on the service user account, see the Limitations of Windows
Certificate Store support when NetBackup services are running in Local Service
account context information in the NetBackup Security and Encryption Guide.
19 Select one of the following options:
■ Click Upgrade to start the upgrade.
■ Click Back to view the previous screens and make any changes, then return
to this screen and click Upgrade.
■ Click Cancel to cancel the upgrade.
After you click Upgrade, the upgrade process begins and a screen appears
that shows you the upgrade progress. This process may take several minutes.
For remote or for cluster upgrades only, right-click on a system in the dialog
box to see the upgrade status. Up to five upgrades occur simultaneously. When
an upgrade is completed, another one begins so that a maximum of five
upgrades are in progress.
20 For remote upgrades only, when all remote upgrades have completed, click
Finish.
21 On the Upgrade Complete screen, select from the following options:
Primary server upgrade 58
Performing silent upgrades on Windows systems
View the log file An upgrade log file provides detailed installation information and shows whether any
errors occurred. This log includes information about the optional installation of the Java
GUI and the JRE.
%ALLUSERSPROFILE%\Veritas\NetBackup\InstallLogs\
Note: When you perform a remote upgrade to multiple computers, this option only
lets you view the log for the local computer. Each computer that you selected for
upgrade contains its own upgrade log file. To view the log file of a remote computer,
open a Windows Explorer window and enter \\<COMPUTERNAME>.
■ If you are done upgrading software on all servers, click the box next to Launch
NetBackup Web UI now and click Finish.
The NetBackup Administration Console starts a Configuration Wizard so that you
can configure your NetBackup environment.
■ If you have more server software to upgrade, click Finish.
You can move on to the next computer and upgrade the necessary server software.
The script shuts down all NetBackup services so that the upgrade can be initiated.
If the script detects that other system processes still maintain a handle on any
NetBackup files, the upgrade fails. To identify which NetBackup processes are still
running, check the NetBackup Install log file at the following location:
%ALLUSERSPROFILE%\Veritas\NetBackup\InstallLogs
After you have manually stopped each of the identified processes, you can run the
upgrade script again.
Note: For Windows 2012/2012 R2/2016 Server Core systems, you can only upgrade
NetBackup with this procedure.
Enter the names of any additional NetBackup primary servers and media
servers that you want to communicate with this host. Include the names of
servers where you plan to install NetBackup later.
If no other servers are to communicate with this host, remove this line from
the script.
■ SET ABORT_REBOOT_INSTALL=0
This line lets you determine how you want the upgrade to continue if a
restart is required. Select from the following settings:
Primary server upgrade 60
Performing silent upgrades on Windows systems
REBOOT="ReallySuppress"
is required to complete the upgrade. Review the article that is shown for
more information:
https://www.veritas.com/content/support/en_US/article.100048600
■ SET ECA_CERT_STORE=cert_store_string
This field is for media servers only. Use this field to specify the external
certificate location in a Windows certificate store. This field is specified in
the form store_name\issuer_DN\subject. This field is required to use an
external certificate from the Windows certificate store.
■ SET ECA_CERT_PATH=path
This field is for media servers only. Use this field to specify the path and
the file name of the external certificate file. This field is required to set up
an external certificate from a file.
■ SET ECA_TRUST_STORE_PATH=path
This field is for media servers only. Use this field to specify the path and
the file name of the file representing the trust store location. This field is
required to set up an external certificate from a file.
■ SET ECA_PRIVATE_KEY_PATH=path
Use this field to specify the path and the file name of the file representing
the private key. This field is required to set up an external certificate from
a file.
■ SET ECA_CRL_CHECK_LEVEL=value
This field is for media servers only. Use this field to specify the CRL mode.
This field is required. Supported values are:
■ USE_CDP: Use the CRL defined in the certificate.
■ SET ECA_CRL_PATH=path
This field is for media servers only. Use this field to specify the path and
the file name of the CRL associated with the external CA certificate. This
field is required only when ECA_CRL_CHECK_LEVEL is set to USE_PATH. If not
applicable, leave this field empty.
■ SET ECA_KEY_PASSPHRASEFILE=path
This field is for media servers only. Use this field to specify the path and
the file name of the file that contains the passphrase to access the keystore.
This field is optional and applies only when setting up an external certificate
from a file.
■ SET INCLUDE_JAVA_GUI_AND_JRE=value
Primary server upgrade 62
Upgrading Linux server software to NetBackup 10.5
Installation of the NetBackup Java GUI and JRE packages is optional for
NetBackup Windows media server installation. This option specifies if the
Java GUI and the JRE packages should be installed, upgraded, or removed.
Supported values for this option are:
■ INCLUDE: Include the Java GUI and JRE when installing or upgrading
NetBackup.
■ EXCLUDE: Exclude the Java GUI and JRE when installing or upgrading
NetBackup. Any preexisting NetBackup Java GUI and JRE packages
are removed.
■ MATCH: Match the existing configuration on the host. Hosts that already
have the Java GUI and JRE components are updated with the latest
versions. The components are excluded for all other hosts.
■ INSTALL_ITA_DATA_COLLECTOR=value
Use this field to specify if Veritas should install the NetBackup IT Analytics
Data Collector. The default the value is 1 which installs the NetBackup IT
Analytics Data Collector. Specify 0 if you don't want the NetBackup IT
Analytics Data Collector installed.
This log includes information about the optional installation of the Java GUI
and the JRE.
Search the installation log for the following error indications:
■ Strings that include Return Value 3.
■ Important log messages are color coded as follows:
Yellow = warning.
Red = error.
to ensure that backups do not interfere with the upgrade. You can also temporarily
modify policies so that backups do not run while you upgrade and reconfigure
NetBackup.
To upgrade Linux server software to 10.5
1 Log on as the root user on the server.
2 If the NetBackup Administration Console is open, you must close it now.
3 (Conditional) For clustered environments, perform the following tasks:
■ If necessary, edit the bp.conf and the vm.conf files as follows:
If a REQUIRED_INTERFACE entry exists, replace it with a CLUSTER_NAME entry.
Otherwise, add a new CLUSTER_NAME entry. This entry should be defined
as the virtual server name.
For a primary server, make sure that the first SERVER entry matches the
CLUSTER_NAME entry for the bp.conf file.
■ Freeze the NetBackup Group so that migrations do not occur while the
inactive nodes are upgraded. Use the command shown:
/opt/VRTSvcs/bin/hagrp -freeze group -persistent
■ If you have a VCS cluster configured, you can freeze the NetBackup Group
by using the Cluster Manager interface or the command line.
■ Before you proceed with a cluster upgrade, refer to the NetBackup Clustered
Primary Server Administrator's Guide for other cluster upgrade requirements.
http://www.veritas.com/docs/DOC5332
4 NetBackup scripts that are not covered in Chapter 1 that you modified are
removed when you run the upgrade script. More information about this topic
is available.
See “About automatic file changes from an upgrade” on page 27.
Save any files that you have modified and want to keep.
5 Navigate to the location where the installation images reside. Enter the
command that is shown to start the upgrade script:
./install
6 Follow the prompts in the installation script to install the NetBackup server
binaries.
Primary server upgrade 64
Upgrading Linux server software to NetBackup 10.5
7 (Conditional: For primary server only) If prompted, provide the name of the
service user account you want to use to start most of the daemons. This prompt
is shown if the installer cannot retrieve the service user value from the bp.conf
file or if the server user is root.
Enter the name of the service user account to be used to start
most of the daemons
Please note:
■ The service username cannot exceed 32 characters and can only contain
English characters.
■ Veritas does not recommend that you use the root user as the service user.
■ You cannot use the nbwebsvc user as the service user.
■ The nbwebgrp group must be a secondary group of the service user.
■ Ownership of the /usr/openv directory changes to the new service user
account that you specified here.
■ Using a service account involves a one-time conversion that may
significantly increase the upgrade time based on your catalog size.
■ If you want to change the service user account after the installation, use
the nbserviceusercmd --changeUser command.
For more details on the service user account, see:
https://www.veritas.com/docs/100048220
8 (Conditional: For primary server only) If prompted, provide the non-root
database user name. The prompt is only shown if the service user is root.
NetBackup 9.0 and later versions support the retention periods that
extend beyond the year 2038. To ensure compatibility with previous
NetBackup versions, all items with an infinite expiration date are
updated to reflect the new infinite expiration date value. This
conversion may extend the time that is required to complete the upgrade.
Review the following article for more information:
https://www.veritas.com/content/support/en_US/article.100048600
Please see the linked article to obtain a more accurate estimate of how
long the conversion may take.
12 (Conditional: For media servers only) When prompted, provide the required
information for the CRL configuration:
13 (Conditional: For media servers only) If you specified Use the CRL from a
file path, you must enter the path to the CRL location:
14 (Conditional: For media servers only) The installer echoes the configuration
information you entered and attempts to retrieve details for the external
certificate:
The external certificate is valid for use with primary server name
How do you want to proceed?
1) Continue the installation using this certificate.
2) Modify the external CA values entered.
3) Abort the installation.
Default option (1):
Primary server upgrade 68
Upgrading Linux server software to NetBackup 10.5
The external certificate is not valid for use with primary server name
How do you want to proceed?
1) Continue the installation and set up external certificates later.
2) Modify the external CA values entered.
3) Abort the installation.
Default option (2):
17 (Conditional: For media servers only) When prompted, indicate how the
upgrade should handle the Java GUI and JRE binaries.
The Java GUI and JRE packages are currently install_state on this
host.
The Java GUI and JRE can be optionally included with NetBackup.
The Java GUI and JRE enable the NetBackup Administration Console
and the Backup, Archive and Restore (BAR) GUI. Choose an option
from the list below.
If you specify 1, the Java and JRE binaries are installed or upgraded, based
on the status of the server. If you specify 2, the Java and JRE binaries are
removed or excluded, based on the status of the server.
Primary server upgrade 69
Upgrading Linux server software to NetBackup 10.5
If you have not downloaded your license from the Veritas Entitlement
Management System portal, answer n. You are then prompted to use a
temporary production license for upgrades. The installer cannot proceed without
a license or a temporary production license, and exits gracefully. More
information is available:
https://www.veritas.com/support/en_US/article.100058779
If you have already downloaded the license, then answer y. You are then
prompted to provide the file path for the license you want to use. When you
provide a license file path, NetBackup validates the file exists, is a valid file for
NetBackup, the contents were not modified, it is not expired etc. After
NetBackup determines the license is valid, the installer shows the license
details and prompts the user to add this license. If user answers y the license
is added. In case of invalid license, installer provides reason why the file is
invalid and prompts you to provide new license file path.
Upgrades from versions earlier than NetBackup 8.1.2 only support the
production licenses that are downloaded from VEMS or the evaluation license.
You cannot use the temporary production license when you upgrade from a
NetBackup version earlier than 8.1.2.
You can also install additional licenses.
19 Starting with NetBackup 10.5, the VRTSpddei.rpm is no longer present in
NetBackup. VRTSpddei.rpm provided the Instant Access and malware scans
of VMware images. In NetBackup 10.5 and later, libguestfs.rpm and
python3-libguestfs.rpm provide this functionality. To continue to use the
Instant Access or malware scans of VMware images functionality, additional
steps may be required. If you see one of these messages that is shown in the
upgrade script output, follow the steps in the article listed.
■ Unable to remove VRTSpddei.rpm during upgrade. Remove this RPM
manually after the upgrade finishes. For more details, see:
https://www.veritas.com/support/en_US/article.100066233
Note: Because of package name changes, native installer methods require additional
steps to upgrade primary servers from NetBackup 7.7.3 and earlier to NetBackup
8.0 and later. You have two options to correctly upgrade your primary servers and
convert to the Veritas packages. You can use the NetBackup installer to upgrade
the primary server to the new Veritas packages. Or you can follow the native
installers procedure and perform the conditional steps. More information is available.
See “To upgrade the Linux primary server binaries using native installers:”
on page 70.
Both of these upgrade options result in the same outcome. Once you have
successfully upgraded to the Veritas packages, you can perform future upgrades
with the installer of your choice.
■ Freeze the NetBackup Group so that migrations do not occur while the
inactive nodes are upgraded. Use the command shown:
/opt/VRTSvcs/bin/hagrp -freeze group -persistent
■ If you have a VCS cluster configured, you can freeze the NetBackup Group
by using the Cluster Manager interface or the command line.
■ Before you proceed with a cluster upgrade, refer to the NetBackup Clustered
Primary Server Administrator's Guide for other cluster upgrade requirements.
http://www.veritas.com/docs/DOC5332
4 NetBackup scripts that are not covered in Chapter 1 that you modified are
removed when you run the upgrade script. More information about this topic
is available.
See “About automatic file changes from an upgrade” on page 27.
Save any files that you have modified and want to keep.
5 Please create the NetBackup installation answer file (NBInstallAnswer.conf)
in the primary server's temporary directory. That directory is usually the /tmp
directory. More information about the answer file and its contents is available.
See “About the NetBackup answer file” on page 146.
6 You can add optional parameters to the NBInstallAnswer.conf file. The
parameters that are shown are examples of some of the parameters you can
add. Veritas recommends that you review the NetBackup answer file section
that is included in this documentation:
■ LICENSE entries
LICENSE entries are only required on primary servers.
For upgrades from pre-NetBackup 10.3 to NetBackup 10.3 or later, the
LICENSE entry is required. LICENSE=TEMP_PRODUCTION |
license_file_path. If you have not downloaded your license from Veritas
Entitlement management portal, you can use TEMP_PRODUCTION. More
information is available:
https://www.veritas.com/support/en_US/article.100058779
Primary server upgrade 72
Silently upgrading NetBackup primary server software on Linux
For upgrades from NetBackup 10.3 or later releases, you don't need to
provide a LICENSE entry if you already have valid and unexpired license
installed.
■ SERVER entries
■ DATABASE_USER
■ VXDBMS_POSTGRESQL_POOLER_ODBC_PORT
■ RBAC_DOMAIN_NAME
Use this field to specify the name of the domain to which the user or the
user group belongs.
■ RBAC_PRINCIPAL_TYPE
Use this field to specify USER or USERGROUP.
■ RBAC_PRINCIPAL_NAME
Use this field to specify the user name or the user group.
More information about the RBAC_* options is available.
See “About RBAC bootstrapping” on page 182.
See “About the NetBackup answer file” on page 146.
8 Download the server package that matches your server platform to a system
with sufficient space. Then extract the contents of the server package file.
Extract the contents of the server package file. Example:
■ For Linux RedHat:
tar -xzvf NetBackup_10.5_LinuxR_x86_64.tar.gz
9 Change to the directory for your desired operating system and copy packages
to the computer to be installed.
Operating system directory:
Primary server upgrade 73
Silently upgrading NetBackup primary server software on Linux
■ VRTSnbclibs.rpm
■ VRTSnbclt.rpm
■ VRTSnbjava.rpm
■ VRTSnbjre.rpm
■ VRTSnbmqbrkr.rpm
■ VRTSnbpck.rpm
■ VRTSnbprimary.rpm
■ VRTSnbslibs.rpm
■ VRTSnbweb.rpm
■ VRTSnetbp.rpm
■ VRTSpbx.rpm
■ VRTSpddea.rpm
■ VRTSpddes.rpm
■ VRTSpddeu.rpm
■ VRTSpostgresql.rpm
10 (Conditional) If you are upgrading from pre-NetBackup 8.0, remove the old
SYMC* packages. The example shown indicates the commands used to remove
the SYMC RPM packages. This process preserves your NetBackup configuration.
rpm -e SYMCnbjava
rpm -e SYMCpddea
rpm -e SYMCnbclt
rpm -e SYMCnbjre
rpm -e SYMCnetbp
rpm -e SYMCpddes
Primary server upgrade 74
Silently upgrading NetBackup primary server software on Linux
11 (Conditional): If the upgrade is from NetBackup 10.1.1 or earlier and you want
to install NetBackup IT Analytics Data Collector; or if you have an unconfigured
NetBackup IT Analytics Data Collector you want to upgrade:
■ Create the /usr/openv/tmp directory with the mkdir -p /usr/openv/tmp
command.
■ Copy the ita_dc.tar.gz tarball from the media's /catalog/anb/ directory
to /usr/openv/tmp.
■ Verify the INSTALL_ITA_DATA_COLLECTOR value is set to YES in the
NBInstallAnswer.confNetBackup file.
If you do not want to install IT Analytics Data Collector, make sure the
INSTALL_ITA_DATA_COLLECTOR value is set to NO in the
NBInstallAnswer.conf file.
Primary server upgrade 75
Silently upgrading NetBackup primary server software on Linux
12 Install the files in the order that is shown with the commands that are shown:
RedHat
Linux rpm -U VRTSnbpck.rpm
rpm -U VRTSpbx.rpm
rpm -U VRTSnbclt.rpm
rpm -U VRTSnbclibs.rpm
rpm -U VRTSnbjre.rpm
rpm -U VRTSnbjava.rpm
rpm -U VRTSpddes.rpm
rpm -U VRTSpddeu.rpm
rpm -U VRTSpddea.rpm
rpm -U VRTSnbcfg.rpm
rpm -U VRTSpostgresql.rpm
rpm -U VRTSnetbp.rpm
rpm -U VRTSnbprimary.rpm
rpm -U VRTSnbmqbrkr.rpm
rpm -U VRTSnbweb.rpm
rpm -U VRTSnbslibs.rpm
13 If you decide to install the Java GUI or the JRE after the installation completes,
additional information is available.
See “Add or Remove Java GUI and JRE after upgrade” on page 144.
■ Prepare for the install by stopping all NetBackup processes and services.
Use the command shown:
UNIX and Linux: /usr/openv/netbackup/bin/bp.kill_all
Windows: install_path\NetBackup\bin\bpdown -f
■ Install the maintenance release.
■ Restart NetBackup with the commands shown:
UNIX and Linux systems: /usr/openv/netbackup/bin/bp.start_all
Windows systems: install_path\NetBackup\bin\bpup -f
2 Set a passphrase for the disaster recovery package. If you do not set a
passphrase, the catalog backups fail. More information is available. Please
see the information about passphrases in the NetBackup Troubleshooting
Guide.
3 If you plan to use role-based access control (RBAC), you must designate a
security administrator. More information is available:
See “About the NetBackup web user interface” on page 145.
See NetBackup Web UI Administrator's Guide.
4 Start any applications on the system that interact with NetBackup. This step
includes any databases or system components being backed up.
5 (Conditional) If you have a clustered primary server, generate a certificate on
the inactive nodes for secure communications. More information is available.
See “Generate a certificate on the inactive nodes of a clustered primary server”
on page 140.
6 (Conditional) If this server is a clustered server, update the other nodes in the
cluster. You can update the other primary servers nodes in the cluster to
NetBackup 10.5 by following standard cluster upgrade process. For complete
details, see the NetBackup Clustered Primary Server Administrator's Guide.
If the NetBackup resource is not online, bring that resource online.
http://www.veritas.com/docs/DOC5332
7 (Conditional) For a primary server that uses external certificate authority (ECA)
or for a media server that skipped ECA configuration, configure the ECA now.
More information is available:
https://www.veritas.com/support/en_US/article.100044300
For more information, see the NetBackup Security and Encryption Guide and
refer to the chapter on external CA and external certificates.
Primary server upgrade 78
Post-install procedure for upgrading to NetBackup 10.5
8 If you have any media servers that you intend to upgrade to NetBackup 10.5,
you may upgrade them now. If you start any media server upgrades, do not
continue with this procedure until the media server upgrades are complete.
10 (Conditional) If your environment uses cloud storage, you need to update the
read and write buffer sizes. More information is available.
See “Post upgrade procedures for Amazon cloud storage servers” on page 202.
11 (Conditional) If you have a NetApp cluster, additional steps may be required.
More information is available.
See “Additional post-upgrade steps for NetApp clusters ” on page 184.
12 (Conditional) For the cloud and the storage servers with SSL enabled, the CRL
validation is enabled by default. Verify if the storage servers are running and
the CRL functionality works correctly. More information is available.
See the NetBackup Cloud Administrator’s Guide.
13 (Conditional) For Amazon configurations, after you upgrade NetBackup and
CloudPoint to the latest version, you must update the credentials. Run the
tpconfig -update command. After the upgrade, the credentials are updated
to only support the AWS IAM role. More information is available.
See the NetBackup Web UI Cloud Administrator’s Guide.
14 Monitor your backup environment to verify that normal NetBackup operation
has resumed.
Primary server upgrade 79
Post-install procedure for upgrading to NetBackup 10.5
15 Upgrade any media servers and clients not already upgraded as time and
backup windows permit. Be sure to upgrade the media servers before you
upgrade the clients. You cannot back up or restore a NetBackup 8.1 client to
a pre-8.1 media server.
See “Upgrading NetBackup media servers to NetBackup 10.5” on page 86.
A client upgrade is the same as a client installation. See the NetBackup
Installation Guide - UNIX and Windows manual for help with the installation.
http://www.veritas.com/docs/DOC5332
Note: All scripts must be stored and run locally. One recommendation is that
scripts should not be world-writable. Scripts are not allowed to be run from
network or remote locations. Any script that is created and saved in the
NetBackup db_ext (UNIX) or dbext (Windows) location needs to be protected
during a NetBackup uninstall.
For more information about registering authorized locations and scripts, review
the knowledge base article:
http://www.veritas.com/docs/000126002
For more information about your specific database agent, review the
documentation for that agent:
http://www.veritas.com/docs/DOC5332
16 (Conditional) For upgrades of NetBackup 8.2 Linux clusters with NAT enabled
to the latest version, the upgrade disables NAT. To turn on NAT and allow the
cluster to monitor the nbmqbroker service that is added to a NetBackup cluster
group, run the command shown:
■ To configure with default ports:
configureMQ -enableCluster -defaultPorts
Platform Links
AIX /etc/rc.netbackup.aix
/etc/rc1.d/K01netbackup ->/etc/init.d/netbackup
/etc/rc2.d/S95netbackup ->/etc/init.d/netbackup
Primary server upgrade 81
Completing your system update after an upgrade
Platform Links
/etc/rc.d/rc1.d/K01netbackup
->/etc/rc.d/init.d/netbackup
/etc/rc.d/rc2.d/S77netbackup
->/etc/rc.d/init.d/netbackup
/etc/rc.d/rc3.d/S77netbackup
->/etc/rc.d/init.d/netbackup
/etc/rc.d/rc5.d/S77netbackup
->/etc/rc.d/init.d/netbackup
/etc/rc.d/rc6.d/K01netbackup
->/etc/rc.d/init.d/netbackup
/etc/init.d/rc2.d/S77netbackup
->/etc/init.d/netbackup
/etc/init.d/rc3.d/S77netbackup
->/etc/init.d/netbackup
/etc/init.d/rc5.d/S77netbackup
->/etc/init.d/netbackup
/etc/init.d/rc6.d/K01netbackup
->/etc/init.d/netbackup
/etc/rc1.d/K01netbackup ->/etc/init.d/netbackup
/etc/rc2.d/S77netbackup ->/etc/init.d/netbackup
Primary server privileges If you upgraded a primary server that allowed nonroot users
to administer NetBackup, you must reconfigure the
permissions and the group. The default permissions and
group on the newly installed files allow only a root user to
perform NetBackup administration.
Update the trust relationship After you upgrade both your source and your target primary
between remote primary server from 8.0 or earlier to 8.1 or later, you must update the
servers for targeted auto trust relationship. Upgrading from NetBackup 8.1 to a later
image replication (AIR) version does not require you to reestablish the trust
relationship. Run the command that is shown on both the
source and the target primary servers to reestablish the trust
relationship:
External certificate authority Configure your external certificate authority. If you opted to
skip the security configuration or if your environment uses
ECA, you may need to configure an ECA. More information
about configuring ECAs is available:
https://www.veritas.com/support/en_US/article.100044300
Update storage servers NetBackup does not update objects such as storage servers
and disk pools every time the storage changes. Storage
changes can result from NetBackup MSDP changes and 3rd
party OST vendor software upgrades. Additionally, changes
to the storage-defined replication topologies that SLP
replication uses as well as import operations require an
update. The user must proactively confirm these changes
through the use of the updatests and updatedp
commands. A NetBackup upgrade may introduce new
functionality you want to use in your environment. Veritas
recommends that you run the updatests and updatedp
commands on the storage servers and disk pools where you
want to use this new functionality. For more information about
the updatests and updatedp commands, see the
NetBackup Commands Reference Guide
4 (Conditional) If you plan to change your NetApp cluster to Vserver mode from
node scope mode, create a detailed image report for each filer. You can
generate this report with the bpimagelist command. The example that is
shown is one possible option. Use whatever options are necessary for your
environment.
bpimagelist –client ndmp_host_name
5 Stop any applications on the system that interact with NetBackup. This step
includes any databases or system components being backed up. Failure to
stop these applications may result in unexpected behavior. Observed behavior
includes aborted upgrades and application failures.
For Oracle users, ensure that no backups are running. Stop the RMAN
processes before you install NetBackup. If you use AIX, you should run
/usr/bin/slibclean as the root user after you stop the RMAN processes.
If you cannot stop your Oracle database, a procedure is available that may let
you install NetBackup with the Oracle database active. More information on
this topic is available.
http://www.veritas.com/docs/TECH158276
6 Stop all NetBackup services.
■ On UNIX and Linux systems: /usr/openv/netbackup/bin/bp.kill_all
■ On Windows systems: install_path\NetBackup\bin\bpdown -f
1 If your media server upgrade is part of the primary server upgrade, you can proceed
to the next step.
3 Upgrade the NetBackup binaries. More information is available about this topic.
4 If you did not get a security certificate, generate the certificate. More information
about this topic is available.
https://sort.veritas.com/netbackup
6 Prepare for the install by stopping all NetBackup processes and services. Use
the command shown:
Linux: /usr/openv/netbackup/bin/bp.kill_all
Windows: install_path\NetBackup\bin\bpdown -f
6 (Conditional) If the media server upgrade is part of a primary server upgrade, skip
this step.
7 (Conditional) If the media server upgrade is part of a primary server upgrade, resume
the primary server upgrade procedure.
Media server upgrade 89
Silently upgrading NetBackup media server software on Linux
Caution: You must remove the NetBackup Nutanix plug-in package before you
upgrade NetBackup Red Hat and SUSE Linux with the native installers. Both the
Nutanix plug-in and NetBackup install the same libraries to the same location, which
results in a failure to upgrade. The upgrade fails with an install of package_name
conflicts with file from package package_name error message.
Use the command that is shown to uninstall the plug-in before attempting the
NetBackup upgrade.
rpm -e VRTSnbntnxahv*
Media server upgrade 90
Silently upgrading NetBackup media server software on Linux
CA_CERTIFICATE_FINGERPRINT=fingerprint
CA_CERTIFICATE_FINGERPRINT=01:23:45:67:89:AB:CD:EF:01:23:45:67:
89:AB:CD:EF:01:23:45:67
■ ECA_CRL_CHECK_LEVEL
Use this field to specify the CRL mode. This field is required. Supported
values are:
■ USE_CDP: Use the CRL defined in the certificate.
■ ECA_CRL_PATH
Use this field to specify the path to the CRL associated with the external
CA certificate. This field is required only when ECA_CRL_CHECK_LEVEL is
set to USE_PATH. If not applicable, leave this field empty.
6 Change to the directory for your desired operating system and copy packages
to the media server.
Operating system directory:
■ For Linux Red Hat:
NetBackup_10.5_LinuxR_x86_64/linuxR_x86/anb
Note: The upgrade of the Java GUI and the JRE is optional. If you do not want
them upgraded, omit the copy and the install of the VRTSnbjava and VRTSnbjre
packages.
Veritas recommends the removal of the old Java GUI and JRE packages if
you decide not to upgrade them.
See “Add or Remove Java GUI and JRE after upgrade” on page 144.
■ VRTSnbcfg.rpm
■ VRTSnbclibs.rpm
■ VRTSnbclt.rpm
■ VRTSnbjava.rpm
■ VRTSnbjre.rpm
■ VRTSnbpck.rpm
■ VRTSnbslibs.rpm
■ VRTSnetbp.rpm
■ VRTSpbx.rpm
■ VRTSpddea.rpm
■ VRTSpddes.rpm
■ VRTSpddeu.rpm
rpm -e SYMCnbjava
rpm -e SYMCpddea
rpm -e SYMCnbclt
rpm -e SYMCnbjre
rpm -e SYMCpddes
rpm -e SYMCnetbp
Media server upgrade 93
Silently upgrading NetBackup media server software on Linux
9 Install the files in the order that is shown with the commands shown:
Note: The upgrade of the Java GUI and the JRE is optional. If you do not want
them upgraded, omit the copy and the install of the VRTSnbjava and VRTSnbjre
packages.
Veritas recommends the removal of the old Java GUI and JRE packages if
you decide not to upgrade them.
See “Add or Remove Java GUI and JRE after upgrade” on page 144.
10 You can remove the old versions of the Java GUI and the JRE if you no longer
plan to use them.
■ Linux:
rpm -e VRTSnbjava.rpm
Media server upgrade 94
Silently upgrading NetBackup media server software on Linux
rpm -e VRTSnbjre.rpm
Chapter 5
MSDP upgrade for
NetBackup
This chapter includes the following topics:
■ Upgrade MSDP media servers and clients using client direct as your environment
allows and make no configuration changes.
If the selected common media server is not a NetBackup 8.1 server, the risk is
restores, verifies, imports, and optimized duplication may fail. If client direct is
used on older clients, you can experience client direct restore errors. This failure
is because of the algorithm change.
■ Upgrade MSDP media servers and clients using client direct as your environment
allows. Modify your list of credentialed media servers for the upgraded storage
servers to only include NetBackup 8.1 servers.
This action effectively revokes access rights for the non-upgraded servers to
the upgraded servers. The risk is previously configured operations may stop
working because of the access change. If you choose this option, you should
make detailed notes about the configuration changes so you can revert those
changes once all media servers are upgraded.
If duplication jobs copy from an 8.1 MSDP to an 8.0 or older MSDP, then create
a storage unit for the older MSDP. Restrict the Media Servers list on that new
storage unit to the 8.1 host. You must change any storage lifecycle policy (SLP)
controlled duplication jobs if they copy from an 8.0 or older MSDP host to an
8.1 MSDP host. Set the Alternate Read Server on the duplication stage to the
8.1 media server.
rolling data conversion is enabled by default and works in the background after the
MSDP conversion completes. Only the data that existed before upgrade is converted.
All new data uses the new SHA-2 fingerprint and does not need conversion.
You can manage and monitor the rolling data conversion using the crcontrol
command. More information about its use is available.
See the NetBackup Deduplication Guide and the NetBackup Commands Reference
Guide.
http://www.veritas.com/docs/DOC5332
■ Upgrading UNIX and Linux clients with the NetBackup upgrade script
■ Upgrade of the UNIX and Linux client binaries with native installers
■ Native UNIX and Linux installers. The native UNIX and Linux installers are
potentially more difficult and require additional steps. More information is
available.
See “Upgrade of the UNIX and Linux client binaries with native installers”
on page 102.
■ VxUpdate. VxUpdate is the replacement for LiveUpdate and lets you schedule
the client upgrade for your client computers. More information is available.
See “About VxUpdate” on page 116.
4 (Conditional) If you plan to change your NetApp cluster to Vserver mode from
node scope mode, create a detailed image report for each filer. You can
generate this report with the bpimagelist command. The example that is
shown is one possible option. Use whatever options are necessary for your
environment.
bpimagelist –client ndmp_host_name
5 Stop any applications on the system that interact with NetBackup. This step
includes any databases or system components being backed up. Failure to
stop these applications may result in unexpected behavior. Observed behavior
includes aborted upgrades and application failures.
For Oracle users, ensure that no backups are running. Stop the RMAN
processes before you install NetBackup. If you use AIX, you should run
/usr/bin/slibclean as the root user after you stop the RMAN processes.
If you cannot stop your Oracle database, a procedure is available that may let
you install NetBackup with the Oracle database active. More information on
this topic is available.
http://www.veritas.com/docs/TECH158276
6 Stop all NetBackup services.
■ On UNIX and Linux systems: /usr/openv/netbackup/bin/bp.kill_all
■ On Windows systems: install_path\NetBackup\bin\bpdown -f
4 After NetBackup checks for required system conditions, press Enter to continue.
Do you want to install the NetBackup client software for this
client? [y,n] (y)
7 If prompted, indicate how the upgrade should handle the Java GUI and the
JRE binaries.
The Java GUI and JRE packages are currently install_state on this
host.
The Java GUI and JRE can be optionally included with NetBackup.
The Java GUI and JRE enable the Backup, Archive and Restore (BAR)
GUI. Choose an option from the list below.
If you specify 1, the Java and JRE binaries are installed or upgraded, based
on the status of the server. If you specify 2, the Java and JRE binaries are
removed or excluded, based on the status of the server.
8 If there are no problems, the installer exits without error.
Caution: You must remove the NetBackup Nutanix plug-in package before you
upgrade NetBackup Red Hat and SUSE Linux with the native installers. Both the
Nutanix plug-in and NetBackup install the same libraries to the same location, which
results in a failure to upgrade. The upgrade fails with an install of package_name
conflicts with file from package package_name error message.
Use the command that is shown to uninstall the plug-in before attempting the
NetBackup upgrade.
rpm -e VRTSnbntnxahv*
CA_CERTIFICATE_FINGERPRINT=fingerprint
CA_CERTIFICATE_FINGERPRINT=01:23:45:67:89:AB:CD:EF:01:23:45:67:
89:AB:CD:EF:01:23:45:67
■ SET ECA_CRL_PATH=path
Use this field to specify the path to the CRL associated with the external
CA certificate. This field is required only when ECA_CRL_CHECK_LEVEL is
set to USE_PATH. If not applicable, leave this field empty.
■ SERVICES=no
Client upgrade 105
Upgrade of the UNIX and Linux client binaries with native installers
■ MERGE_SERVER_LIST=value
AIX CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/RS6000/AIX7.1/
CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/RedHat4.18.0/
CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/SuSE4.4.73
CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/
Linux-s390x/IBMzSeriesSuSE5.3.18
Client upgrade 106
Upgrade of the UNIX and Linux client binaries with native installers
CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/
Linux-ppc64le/IBMpSeriesSuSE5.3.18
CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/Solaris/Solaris10/
CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/Solaris/Solaris_x86_10_64/
Note: Where supported, the upgrade of the Java GUI and the JRE is
optional. If you don't want to upgrade them, don't copy or install the
VRTSnbjava and VRTSnbjre packages. Veritas recommends that you remove
the old Java GUI and JRE packages if you decide not to upgrade them.
It is recommended to remove the old Java GUI and JRE packages if you
decide not to upgrade them.
See “Add or Remove Java GUI and JRE after upgrade” on page 144.
AIX VRTSnbpck.image
VRTSpbx.image.gz
VRTSnbclt.image.gz
VRTSnbclibs.image.gz
VRTSnbjre.image.gz
VRTSnbjava.image.gz
VRTSpddea.image.gz
VRTSnbcfg.image.gz
Client upgrade 107
Upgrade of the UNIX and Linux client binaries with native installers
Linux VRTSnbpck.rpm
VRTSpbx.rpm
VRTSnbclt.rpm
VRTSnbclibs.rpm
VRTSnbjre.rpm
VRTSnbjava.rpm
VRTSpddeu.rpm
VRTSpddea.rpm
VRTSnbcfg.rpm
Solaris .pkg_defaults
VRTSnbpck.pkg.gz
VRTSpbx.pkg.gz
VRTSnbclt.pkg.gz
VRTSnbclibs.pkg.gz
VRTSpddea.pkg.gz
VRTSnbcfg.pkg.gz
7 (Conditional) For Solaris and AIX, extract the compressed package files with
the command shown:
gunzip VRTS*.*
VRTSnbpck.pkg
VRTSpbx.pkg
VRTSnbclt.pkg
VRTSnbclibs.pkg
VRTSnbjre.pkg
VRTSnbjava.pkg
VRTSpddea.pkg
VRTSnbcfg.pkg
9 (Conditional) If you are upgrading from pre-NetBackup 8.0, remove the old
SYMC* packages. The example shown indicates the commands used to remove
the SYMC RPM packages. This process preserves your NetBackup configuration.
rpm -e SYMCnbjava
rpm -e SYMCpddea
rpm -e SYMCnbclt
rpm -e SYMCnbjre
10 Install the files in the order that is shown with the command shown:
Note: The upgrade of the Java GUI and JRE is optional. If you do not want
them upgraded, omit the copy and the install of the VRTSnbjava and VRTSnbjre
packages.
It is recommended to remove the old Java GUI and JRE packages if you decide
not to upgrade them.
See “Add or Remove Java GUI and JRE after upgrade” on page 144.
Client upgrade 109
Upgrade of the UNIX and Linux client binaries with native installers
11 (Conditional) If you do not have the answer file in place or you do not populate
it correctly, you receive the error message shown:
WARNING: There is no answer file present and no valid bp.conf.
Therefore, security configuration is not complete. Manual steps
are required before backups and restores can occur. For more
information:
https://www.veritas.com/support/en_US/article.000127129
■ Solaris:
pkgrm VRTSnbjava
pkgrm VRTSnbjre
■ AIX
installp –u VRTSnbjre
installp –u VRTSnbjava
Customers who use the NetBackup installation script for their UNIX and Linux clients
only see a single change to the installation behavior. The NetBackup installation
script no longer copies the installation package into the /usr/openv/pack/ directory
on the client. A successful installation or upgrade is recorded in the
/usr/openv/pack/install.history file.
For AIX
Client upgrade 111
Upgrade of the UNIX and Linux client binaries with native installers
User attempts to install # installp -ad VRTSnbpck.image all Use the lslpp –L package_name
the binaries on top of command to determine the name of the
package VRTSnbpck.image is already
the same version of the installed package. Uninstall this package and
installed
binaries. then retry the operation.
User attempts to install # installp -ad VRTSnbcfg.image all Refer to the documentation for the correct
the binaries in the image package installation order. More
error: Failed dependencies:
incorrect order. information is also available in the error which
VRTSnbclt >= 8.1.0.0 is needed by lists the dependent packages.
VRTSnbcfg-version-platform
See “To upgrade the UNIX or Linux client
binaries using native installers:” on page 103.
User attempts to install # installp –d VRTSnbclt.image all Use the lslpp –L package_name
an older version of a command to determine the name of the
WARNING:
binary over the top of a installed package. Uninstall this package and
newer version of the file then retry the operation.
binary. /usr/openv/lib/java/nbvmwaretags.jar
from install of
VRTSnbclt-version-platform
conflicts with file from package
VRTSnbclt-version-platform
For Linux
User attempts to install # rpm -U VRTSnbpck.rpm Use the rpm command to determine the name
the binaries on top of of the installed package. Uninstall this
package
the same version of the package and then retry the operation.
VRTSnbpck.rpm-version-platform is
binaries.
already installed
User attempts to install # rpm -U VRTSnbcfg.rpm Refer to the documentation for the correct
the binaries in the RPM installation order. More information is
error: Failed dependencies:
incorrect order. available.
VRTSnbclt >= 8.1.0.0 is needed by
See “To upgrade the UNIX or Linux client
VRTSnbcfg-version-platform
binaries using native installers:” on page 103.
User attempts to install # rpm -U VRTSnbclt.rpm Use the rpm command to determine the name
an older version of a of the installed package. Uninstall this
file
binary over the top of a package and then retry the operation.
/usr/openv/lib/java/nbvmwaretags.jar
newer version of the
from install of
binary.
VRTSnbclt-version-platform
conflicts with file from package
VRTSnbclt-version-platform
Client upgrade 112
Upgrade of the UNIX and Linux client binaries with native installers
For Solaris
Client upgrade 113
Upgrade of the UNIX and Linux client binaries with native installers
pkgadd -a .pkg_defaults -d
VRTSnbpck.pkg VRTSnbpck
Installing NB-Pck.
## Installing part 1 of 1.
User attempts to install # pkgadd -a .pkg_defaults -d Refer to the documentation for the correct
the binaries in the VRTSnbclt.pkg VRTSnbclt package installation order. More information
incorrect order. is available.
ERROR: VRTSnbpck >=8.1.0.0 is
required by VRTSnbclt. See “To upgrade the UNIX or Linux client
checkinstall script suspends binaries using native installers:” on page 103.
User attempts to install # pkgadd -a .pkg_defaults -d Use the pkginfo command to determine the
an older version of a VRTSnbclt.pkg VRTSnbclt name of the package that is currently installed.
binary over the top of a Uninstall this package and then retry the
Processing package instance
newer version of the operation.
<VRTSnbclt> from
binary.
</root/80packages/Solaris/
Solaris_x86_10_64/VRTSnbclt.pkg>
(i386) 8.1.0.0
■ About VxUpdate
■ Repository management
■ Manually initiating upgrades from the media server or client using VxUpdate
About VxUpdate
VxUpdate provides a policy-based upgrade tool for media servers and clients. By
using the policy format, Veritas provides a simplified tool for media server and client
upgrades. No additional external tools are required and the configuration is in a
familiar policy-based format, similar to a backup policy. Signed packages are verified
and installed into the VxUpdate repository on the primary server. Once the packages
are installed, they become available for use with deployment policies. Additionally,
you can use the deployment policies to automate the installation of emergency
engineering binaries, as provided by Veritas.
NetBackup Deployment Management with VxUpdate 117
Commands used in VxUpdate
Note: You can only cancel queued deployment jobs. Once a VxUpdate job enters
the active state it cannot be canceled.
The deployment policies are not located with the other policies in the NetBackup
Administrative Console. Deployment policies are located in the NetBackup
Administration Console under Deployment Management > Deployment Policies.
To successfully create and use deployment policies, Veritas recommends:
Table 7-1
Step Action Additional information
3 (Optional) Manually run the upgrade See “Manually initiating upgrades from
from the primary server, media server, the primary server using VxUpdate”
or the client on page 126.
■ nbinstallcmd
Use the nbinstallcmd command to initiate the deployment policies from the
command line. You can also use the command to initiate on-demand deployment
jobs. This command is located on all hosts in the NetBackup environment.
More information about these and other related commands is available.
NetBackup Commands Reference Guide
Repository management
VxUpdate uses a repository that resides on the primary server. The repository
contains all packages that you can deploy to media servers and clients. Your
repository can contain upgrade packages, emergency engineering binaries, and
hotfixes.
Veritas signs the VxUpdate packages. Attempts to populate the repository with
unofficial or unsigned NetBackup packages fails. These packages are referenced
in the deployment policies that install NetBackup on target hosts.
Depending on the packages added, the repository can grow large. When you use
the NetBackup web UI or the nbrepo command to populate the repository, be
mindful of the required disk space. Confirm that you have sufficient space on your
primary server for all packages that are required for your environment. The primary
server must have enough disk space to store packages for the NetBackup versions
and platforms that are specified in deployment policies.
For Linux, the repository is in /usr/openv/var/global/repo. For Windows, the
repository is in install_path\NetBackup\var\global\repo.
The package types you can load into the repository include:
■ VxUpdate media server and client packages
You can upgrade NetBackup media servers and clients to a newer version of
NetBackup with VxUpdate. These packages are slightly different from standard
NetBackup media server and client packages. The packages include additional
components to support the various VxUpdate operations.
■ Emergency engineering binaries (EEBs) and hotfixes
You can use VxUpdate to deploy emergency engineering binaries and hotfixes
to NetBackup 8.1.2 and later media servers and clients. You can obtain VxUpdate
formatted EEBs from support in the same way you obtain traditional EEBs.
These EEBs are only for NetBackup version 8.1.2 and later. Any media server
or client hotfixes that Veritas creates for NetBackup 8.1.2 and later releases
include VxUpdate formatted fixes.
NetBackup Deployment Management with VxUpdate 119
Repository management
repository without the use of the NetBackup web UI or the nbrepo command. The
NetBackup web UI and the nbrepo command verify and populate the repository
with NetBackup packages.
VxUpdate can only use the Veritas signed packages that you added to the
NetBackup package repository. Use the nbrepo command or the NetBackup web
UI to add packages to the repository. These options add metadata to the EMM
database and place the packages in the repository directory structure on the file
system. You can use either of these options to list the contents of the package
repository as well as the details about individual packages.
To add packages to the NetBackup package repository with the nbrepo
command:
1 Navigate to the admincmd directory from a command prompt.
Linux: /usr/openv/netbackup/bin/admincmd
Windows: install_path\NetBackup\bin\admincmd\
2 Use the nbrepo command with the -a option:
nbrepo -a package_path
3 Use the nbrepo command with the -d option to delete any unused packages.
nbrepo -d package_identifier
Example: nbrepo -d 6
4 More information about the nbrepo command is available.
NetBackup Commands Reference Guide
Note: You must add packages to the VxUpdate repository before you can create
a working deployment policy. You can create deployment policies without packages
in the repository, but those policies fail to run successfully.
For more information regarding adding packages, see the Repository Management
section within the NetBackup Upgrade Guide.
NetBackup Deployment Management with VxUpdate 122
Deployment policy management
■ Media server: Specify the media server from drop-down. The media server
that is specified is used to connect and transfer files to the NetBackup hosts
that are included in the policy. The media server also caches the files from
the NetBackup repository. The media server must be version NetBackup
8.1.2 or later. Since the repository resides on the primary server, the primary
server is the default value for the media server field.
When you upgrade media servers, the Media server drop-down is
automatically set to the primary server and cannot be changed.
■ Java GUI and JRE: Specify if you want the Java GUI and the JRE upgraded
on the target systems. The three options include:
■ INCLUDE: Install or upgrade the Java GUI and JRE components on the
specified computers.
■ EXCLUDE: Exclude the Java GUI and JRE components from the
specified computer. Any preexisting NetBackup Java GUI and JRE
packages are removed.
■ MATCH: Preserve the current state of the Java GUI and JRE
components. The components are upgraded if they are present on the
pre-upgraded system. The components are not installed if they are not
present on the pre-upgraded system.
If the check box is selected, the default value is 3. If you do not select the
check box, no limit is enforced for the simultaneous upgrade jobs.
You can set unlimited simultaneous upgrade jobs through command line
interface by setting the value as 0.
■ Select hosts: Select hosts from the Available hosts list and select Add
to add hosts to the deployment policy. The list is generated from hosts in
the host database and backup policies. Once you select Add, the hosts
are shown under Selected hosts.
Deployment policies can contain either media servers or clients but not
both. When you select the package you want installed, the list of available
hosts is filtered to media servers or clients.
Note: Please be aware that adding multiple different schedule types to the
same deployment schedule window has unpredictable results. VxUpdate
has no defined behavior to determine which schedule type runs first. If a
single deployment schedule window has precheck, stage, and install jobs,
there is no way to specify the order in which they run. The precheck or the
stage schedules can fail, but the install completes successfully. If you plan
to use precheck, stage, and install schedules, it is recommended that you
create separate schedules and separate windows for each.
■ Starts: Specify the date and time you want the policy to start in the text
field or with the date and the time spinner. You can also click the calendar
icon and specify a date and time in the resulting window. You can select a
schedule by clicking and dragging over the three-month calendar that is
provided at the bottom of the window.
■ Ends: Specify the date and time you want the policy to end as you specified
the start time.
■ Duration: Optionally, you can specify a duration in days, hours, minutes,
and seconds instead of an end time for the policy. The minimum value is
5 minutes and the maximum is 99 days.
■ Select Add/OK and the schedule is created. Select OK to save and create
your policy.
NetBackup Deployment Management with VxUpdate 125
Deployment policy management
9 A Security tab appears when you select a deployment package that contains
support for external certificate authorities.
By default, the Use existing certificates when possible option is selected.
This option instructs NetBackup to use the existing NetBackup CA or external
CA certificates, if available.
Note: If you specify this option and certificates are not available, your upgrade
fails.
Deselecting the Use existing certificates when possible option lets you
specify the location for external certificate authority information for both UNIX
and Linux computers and Windows computers.
Deselecting this option does not allow the user to change the security
configuration settings during the upgrade.
10 Windows clients have Use Windows certificate store selected by default.
You must enter the certificate location as Certificate Store Name\Issuer
Distinguished Name\Subject Distinguished Name.
Note: You can use the $hostname variable for any of the names in the certificate
store specification. The $hostname variable evaluates at run time to the name
of the local host. This option provides flexibility when you push NetBackup
software to a large number of clients.
Then select the Certificate Revocation List (CRL) option from the radio buttons
shown:
■ Do not use a CRL. No additional information is required.
■ Use the CRL defined in the certificate. No additional information is
required.
■ Use the CRL at the following path: You are prompted to provide a path
to the CRL.
11 For both media servers and clients that select the From certificate file path
(for file-based certificates) option, specify the information as shown:
NetBackup Deployment Management with VxUpdate 126
Manually initiating upgrades from the primary server using VxUpdate
■ Certificate file: This field requires you to provide the path to the certificate
file and the certificate file name.
■ Trust store location: This field requires you to provide the path to the trust
store and the trust store file name.
■ Private key path: This field requires you to provide the path to the private
key file and the private key file name.
■ Passphrase file: This field requires you to provide the path of the
passphrase file and the passphrase file name. This field is optional.
■ Then specify the correct CRL option for your environment:
■ Do not use a CRL. No additional information is required.
■ Use the CRL defined in the certificate. No additional information is
required.
■ Use the CRL at the following path: You are prompted to provide a
path to the CRL.
See “Manually initiating upgrades from the media server or client using VxUpdate”
on page 131.
To manually initiate an upgrade of all media servers or clients in a policy from
the administration console
1 In the NetBackup Administration Console, navigate to Deployment
Management > Deployment Policies.
2 In the middle pane, expand the primary server, and select the policy you want
to run.
3 Right-click on the policy you want to start, and select Manual Deployment.
4 Alternatively, after selecting the policy you want to run, you can select Actions
> Manual Deployment.
To manually initiate an upgrade of a specific host in a policy from the
administration console
1 Select NetBackup Management > Host Properties > Media Servers or
NetBackup Management > Host Properties > Clients in the NetBackup
Administrative Console.
2 Right click on the host you want to upgrade in the right pane.
3 Select Upgrade Host.
4 In the Upgrade Host dialog:
■ Select the package you want to use from the Package drop-down.
■ Specify the type of schedule you want to run from the Type drop-down.
■ Select the media server you want to use from the Media server drop-down.
When you upgrade media servers, the Media server drop-down is
automatically set to the primary server and cannot be changed.
■ Confirm that the host you want upgraded is listed under Selected hosts.
NetBackup Deployment Management with VxUpdate 128
Manually initiating upgrades from the primary server using VxUpdate
Note: If you specify this option and certificates are not available, the upgrade
fails.
Deselecting the Use existing certificates when possible option lets you
specify the location for external certificate authority information for both UNIX
and Linux computers and Windows computers.
Deselecting this option does not allow the user to change the security
configuration settings during the upgrade.
6 Windows clients have Use Windows certificate store selected by default.
You must enter the certificate location as Certificate Store Name\Issuer
Distinguished Name\Subject Distinguished Name.
Note: You can use the $hostname variable for any of the names in the certificate
store specification. The $hostname variable evaluates at run time to the name
of the local host. This option provides flexibility when you push NetBackup
software to a large number of clients.
Then select the Certificate Revocation List (CRL) option from the radio buttons
shown:
■ Do not use a CRL. No additional information is required.
■ Use the CRL defined in the certificate. No additional information is
required.
■ Use the CRL at the following path: You are prompted to provide a path
to the CRL.
7 For both UNIX and Linux clients and Windows clients that select the From
certificate file path (for file-based certificates) option, specify the information
as shown:
NetBackup Deployment Management with VxUpdate 129
Manually initiating upgrades from the primary server using VxUpdate
■ Certificate file: This field requires you to provide the path to the certificate
file and the certificate file name.
■ Trust store location: This field requires you to provide the path to the trust
store and the trust store file name.
■ Private key path: This field requires you to provide the path to the private
key file and the private key file name.
■ Passphrase file: This field requires you to provide the path of the
passphrase file and the passphrase file name. This field is optional.
■ Then specify the correct CRL option for your environment:
■ Do not use a CRL. No additional information is required.
■ Use the CRL defined in the certificate. No additional information is
required.
■ Use the CRL at the following path: You are prompted to provide a
path to the CRL.
Note: You can also launch a client upgrade job from the Policies section of
the NetBackup Administrative Console. Select NetBackup Management >
Policies in the NetBackup Administrative Console. In the middle pane, select
Clients. Then right-click on the client you want to upgrade in the right pane
and select Upgrade Host. Then follow the procedure shown. This procedure
is only applicable to clients, not media servers.
To manually initiate an upgrade from the command line for all media servers
or clients in a policy
Use this procedure to manually start an upgrade for all media servers or clients in
a policy.
Note: This procedure starts the upgrade for all media servers or clients in the
specified policy. You can start an upgrade on selected media servers or clients.
More information is available.
To manually initiate an upgrade from the command line for selected hosts in a policy
NetBackup Deployment Management with VxUpdate 130
Manually initiating upgrades from the primary server using VxUpdate
Note: This procedure starts the upgrade on selected media servers and client in
the specified policy. You can start an upgrade for all media servers and clients in
a policy. More information is available.
To manually initiate an upgrade from the command line for all media servers or
clients in a policy
Where:
■ policy_name is the name of the deployment policy
■ schedule is the name of the schedule
■ filename is the name of a file that contains a list of media servers or clients
to upgrade.
■ client1, client2, clientN is a list of media servers or clients to upgrade.
You can manually initiate the upgrade of a single client from the command line
without an associated policy. The options required for the nbinstallcmd command
vary depending on your security configuration. Please refer to the nbinstallcmd
NetBackup Deployment Management with VxUpdate 131
Manually initiating upgrades from the media server or client using VxUpdate
command documentation for a list of all possible options and examples of command
usage.
NetBackup Commands Reference Guide
Note: You can only launch updates on the local media server or client. You cannot
use the nbinstallcmd command on a media server or client to launch jobs on other
media servers or clients. If you want to launch updates on other media servers and
clients, you must initiate them from the primary server.
VxUpdate also provides the ability to launch upgrades from the primary server with
the command line. More information is available.
See “Manually initiating upgrades from the primary server using VxUpdate”
on page 126.
The nbinstallcmd version on a back-level host is not the current nbinstallcmd
version when you initiate a non-policy based upgrade directly on the target client
or media server. Refer to the NetBackup Commands Reference Guide for the
currently installed version of NetBackup for the exact format of nbinstallcmd
command.
Because of this older version of nbinstallcmd, exceptions to normal VxUpdate
behavior include:
■ If your primary server uses both NetBackup certificate and an external certificate,
and your target media server or client is at NetBackup 8.1.2: Running a
non-policy based upgrade directly on the target host is not supported. You must
upgrade with one of the options shown:
■ Upgrade the client or the media server using VxUpdate from the primary
server.
NetBackup Deployment Management with VxUpdate 132
Manually initiating upgrades from the media server or client using VxUpdate
■ If the client or the media server is at NetBackup 8.2 or earlier, the -components
flag is not available. This flag was introduced in NetBackup 8.3 to enable optional
installation of the NetBackup Java GUI and JRE. When you run an ad-hoc
nbinstallcmd on a client or a media server at NetBackup 8.2 or earlier, the
-components javagui_jre option defaults to MATCH. This value causes the
upgrade to match the Java GUI and JRE status of the pre-upgrade host. If the
pre-upgrade host had Java GUI and JRE installed, it remains installed after
upgrade. If the pre-upgrade host did not have Java GUI and JRE installed, it is
not installed after upgrade.
To start a media server or client initiated deployment job based on an existing
policy
1 Navigate to the binary directory from a command prompt.
UNIX or Linux: /usr/openv/netbackup/bin
Windows: install_path\netbackup\bin
2 Use the nbinstallcmd as shown:
nbinstallcmd -policy policy -schedule schedule -master_server
name
If the job initiated successfully, you are returned to the command prompt without
an error message.
Note: When you initiate a media server upgrade with the nbinstallcmd
command, you must include both the -master_server and the -media_server
options. In this case, the value for both these options must be the same.
3 Monitor upgrade status with the NetBackup administrator and the Activity
Monitor in the NetBackup Administrative Console.
You can start a media server or client initiated deployment job without an associated
policy from the command line. The options that are required for the nbinstallcmd
command vary depending on your security configuration and the NetBackup version
NetBackup Deployment Management with VxUpdate 133
Deployment job status
Deployment policies use a simplified naming scheme for operating system and
hardware values. Use the values as shown for the bpplclients command:
debian x64
redhat x64
suse x64
redhat ppc64le
suse ppc64le
redhat zseries
suse zseries
NetBackup Deployment Management with VxUpdate 134
Deployment job status
aix rs6000
solaris sparc
solaris x64
windows x64
Security certificates are not deployed as part of the VxUpdate upgrade if the Security
level for certificate deployment is set to Very High. This setting is located in the
Global security settings.
If you cannot communicate with your clients after you use VxUpdate to upgrade
your clients, please ensure that the proper security certificates were issued during
upgrade. You may need to manually deploy the certificates. Refer to the following
article that is shown for additional details:
https://www.veritas.com/content/support/en_US/article.100039650
Your deployment job may receive a status code 7207. This error can occur if
NetBackup precheck or upgrade processes take longer than expected to finish or
never finish. To configure the amount of time VxUpdate waits before jobs end with
status 7207, you can define the following values in the NetBackup configuration on
the primary server.
VXUPDATE_CLIENT_READ_TIMEOUT_SECONDS
This value controls how long the precheck operations and the client upgrade
operations are allowed to take, in seconds. The default value is 1800, or 30 minutes.
It can be decreased to as little as 600, 10 minutes, or increased to as much as
3600, 60 minutes.
VXUPDATE_SERVER_READ_TIMEOUT_SECONDS
This value controls how long server upgrade operations are allowed to take, in
seconds. The default value is 2700, or 45 minutes. It can be decreased to as little
as 600, 10 minutes, or increased to as much as 5400, 90 minutes.
See the NetBackup Commands Reference Guide for details on how to use the
bpsetconfig command to add values to the NetBackup configuration of a primary
server.
NetBackup Deployment Management with VxUpdate 135
EEB management view
■ Removing a clustered media server by migrating all data to a new media server
Note: For security purposes, do not create web server users or groups with
administrator or superuser privileges.
You can use numerous procedures to create users and groups in operating systems.
Some specific approaches are shown, but other methods may accomplish the same
goal. The home directory path, user name, and group names are not hard-coded,
and can be changed. The default local user name is nbwebsvc, and the default local
group name is nbwebgrp. The user and group must have sufficient permissions to
run daemons.
More information about this topic is available.
See “Upgrade requirements for UNIX and Linux” on page 191.
Please be aware of the operating system-specific account and group requirements:
■ In Linux clustered environments, make sure that the local accounts are defined
consistently on all cluster nodes. The UID must be the same for each local
account. You can use LDAP accounts on UNIX.
■ For Windows clustered primary servers, you must use a domain account. You
can use a domain account for non-clustered environments, but it is not required.
Reference 138
NetBackup primary server web server user and group creation
■ For Windows clustered primary servers, you must use a domain group.
The NetBackup primary server installation fails if any of these requirements are not
met. On Windows, you are asked to provide the password for the user account as
part of the installation process.
Note: If the password associated with the web server account expires after initial
configuration, NetBackup provides no notification the password has expired. This
behavior is normal and expected, as the operating system manages the account
and the password.
As long as the web server remains active, the account and the web server continue
to operate normally.
When the web server is restarted, or if you attempt to restart the nbwmc service, the
service fails to start, due to the expired password. Navigate to the appropriate area
in the operating system, supply the correct password, and restart the service.
More information about the web services account and group is available. See the
NetBackup Security and Encryption Guide and the section on the web services
account.
To create the local user account and the local group:
1 Create a local group.
■ Linux:# groupadd nbwebgrp
■ Windows: C:\>net localgroup nbwebgrp /add
3 (Conditional) For Windows only, make the user a member of the group:
C:\>net localgroup nbwebgrp nbwebsvc /add
4 (Conditional) For Windows only, grant the Log on as a service right to the
user:
■ Go to Control Panel > Administrative Tools > Local Security Policy.
■ Under Security Settings, click Local Policies > User Rights Assignment.
■ Right-click on Log on as a service and select Properties
■ Add the local user. The default local user name is nbwebsvc.
Reference 139
NetBackup database user
■ Save your changes and close the Properties dialog for Log on as a
service.
You can use numerous procedures to create this user. Some specific approaches
are shown, but other methods may accomplish the same goal. The user must have
sufficient permissions to run daemons. More information about this topic is available.
See “Upgrade requirements for UNIX and Linux” on page 191.
Be aware of the operating system-specific account requirements:
■ A separate database user account is required for Linux only if the service account
is root. If the service account is non-root, you do not need to create an additional
user.
■ In Linux clustered environments, make sure that the local accounts are defined
consistently on all cluster nodes. The UID must be the same for each local
account. You can use LDAP accounts on UNIX.
■ For Windows clustered primary servers, you must use a domain account. You
can use a domain account for non-clustered environments, but it is not required.
The NetBackup primary server installation fails if these requirements are not met.
On Windows, you are asked to provide the password for the user account as part
of the installation process.
Reference 140
Generate a certificate on the inactive nodes of a clustered primary server
Note: If the password associated with the account expires after initial configuration,
NetBackup provides no notification the password has expired. This behavior is
normal and expected, as the operating system manages the account and the
password.
As long as the NetBackup catalog remains active, NetBackup continues to operate
normally.
When you attempt to restart NetBackup, the restart fails due to the expired password.
Navigate to the appropriate area in the operating system, supply the correct
password, and restart the service.
2 (Conditional) For Windows only, grant the Log on as a service right to the
user:
■ Go to Control Panel > Administrative Tools > Local Security Policy.
■ Under Security Settings, click Local Policies > User Rights Assignment.
■ Right-click on Log on as a service and select Properties.
■ Add the local user.
■ Save your changes and close the Properties dialog for Log on as a
service.
Note: Unless otherwise indicated, all commands are issued from the inactive node
Reference 141
About the NetBackup Java Runtime Environment
include all the directories that a standard JRE installation includes, such as man
and plugin.
Products that install the JRE:
■ NetBackup primary server, media server, or UNIX and Linux client software
■ NetBackup Java Remote Administration Console
Starting with NetBackup 8.3, the Java GUI and the JRE packages are optional for
Linux and Windows media servers and UNIX and Linux clients.
As with previous releases, the Java GUI and JRE packages are installed
automatically on all primary servers because they are required. The Java GUI and
the JRE are not part of the default installation on Windows clients. Install the Java
Remote Administration Console if you require this functionality on your Windows
clients.
The various NetBackup installation methods allow the user the choice to install or
not install the Java GUI and JRE packages. More information about installing or
removing the Java GUI and the JRE after install or upgrade is available.
See “Add or Remove Java GUI and JRE after upgrade” on page 144.
Previously, the JRE package that is installed with NetBackup was only updated
when you upgraded to a later release of the software. You can use the
nbcomponentupdate utility to update the JRE to a supported version for the products
shown:
■ NetBackup primary server, media server, or UNIX and Linux client software
■ NetBackup Java Remote Administration Console
Note: You cannot use this utility to update the JRE for the NetBackup Plug-in for
VMware vCenter.
If your system is running NetBackup 8.0 or later, use Table A-1 to determine the
location of the nbcomponentupdate utility.
UNIX or /usr/openv/java/nbcomponentupdate
Linux
Reference 143
About the NetBackup Java Runtime Environment
Caution: Do not stop the utility while the JRE update is in progress. This action
can cause the product that uses the JRE, such as NetBackup, to become unstable.
If there are additional versions of the JRE installed on your system for other
applications, the NetBackup JRE does not interfere with them. The NetBackup JRE
does not provide integration with web browsers and does not allow Java Applets
or Web Start to run. For that reason, the NetBackup JRE cannot be used in a
browser-based attack that uses Java Applet or Web Start vulnerabilities.
More information about NetBackup JRE alerts is available.
http://www.veritas.com/docs/TECH50711
Reference 144
Add or Remove Java GUI and JRE after upgrade
rpm -U VRTSnbjava.rpm
Debian Re-run the Debian install script and specify the correct value to add the
Java GUI and the JRE packages.
■ On Windows, access the installation media, and run the packages shown:
■ Veritas NetBackup JRE.msi
rpm -e VRTSnbjre
installp –u VRTSnbjava
Debian Re-run the Debian install script and specify the correct value to remove
the Java GUI and the JRE packages.
Reference 145
About the NetBackup web user interface
■ On Windows
■ Select Start > Settings > Control Panel.
■ In the Control Panel window, select the appropriate utility for installed
programs and applications.
■ From the Currently Installed Programs list, select Veritas NetBackup
Java and click Remove.
■ From the Currently Installed Programs list, select Veritas NetBackup
JRE and click Remove.
INCLUDE_JAVA_GUI_AND_JRE Media and clients All UNIX and Linux media servers and
clients: No
INSTALL_PATH Primary, media, UNIX and Linux No, see the option details for
and client additional information.
Windows: Yes
Windows: Yes
ABORT_REBOOT_INSTALL
■ Default value: 0
■ Required: No.
■ ABORT_REBOOT_INSTALL 0 | 1
ACCEPT_EULA
■ Description: This option specifies if you accept the terms of the EULA and want
to proceed with the installation or the upgrade.
■ Applicable platforms: UNIX and Linux
■ Default value: None
■ Required: No
■ ACCEPT_EULA = yes | no
ACCEPT_REVERSE_CONNECTION
■ Description: Use this option to identify how a NAT client connects with a
NetBackup host. Accepted values are TRUE and FALSE. Set this option to TRUE
if NetBackup needs to support NAT, otherwise set it to FALSE. Set
ACCEPT_REVERSE_CONNECTION=FALSE if:
ADDITIONALSERVERS
■ Description: Use this option to Include NetBackup media servers that are used
to proxy security requests to the primary server. List only the servers that were
added since the last installation of this host. The install process combines the
existing set of servers with the new ones. The use of IP addresses is not
supported. Valid input values are a comma-separated list of fully qualified
computer names.
■ Applicable platforms: Windows only.
Reference 155
About the NetBackup answer file
ALLOW_LONG_NBDB_MIGRATION_TIME
ALLOW_PRE_90_UPGRADE
■ Description: This field is for primary servers only. This value determines if the
upgrade from pre-NetBackup 9.0 releases to NetBackup 9.0 and later can
proceed. The upgrade includes the infinite expiration conversion process. This
conversion only takes place when you upgrade from pre-NetBackup 9.0 to
NetBackup 9.0 or later. The upgrade behavior and need for this option depend
on your primary server platform.
■ Windows
This value is required for silent upgrades of Windows primary servers. Specify
1 to allow the upgrade to continue, specify 0 to prevent the upgrade. This
value is ignored during an interactive Windows primary server upgrade.
Depending on the size of the NetBackup catalog and the required conversion
time, you may be asked if you want to continue the upgrade.
■ Linux
For Linux primary servers, specify yes or no to eliminate user prompts. If the
infinite expiration conversion is expected to add length to the upgrade
process, a value of yes means the upgrade proceeds. A value of no means
the upgrade stops. If this value is not specified, NetBackup prompts you if
you want to continue with the upgrade.
Reference 156
About the NetBackup answer file
NetBackup 9.0 and later versions support the expiration dates that extend beyond
the year 2038. To ensure compatibility with previous NetBackup versions, all
items with an infinite expiration date are updated to reflect the new infinite
expiration date value. This conversion may extend the time that is required to
complete the upgrade. Review the article that is shown for more information:
https://www.veritas.com/content/support/en_US/article.100048600
■ Applicable platforms: Both UNIX and Windows.
■ Default value: None
■ Required: Platform and upgrade method dependent.
■ ALLOW_PRE_90_UPGRADE=yes|no (UNIX)
ALLOW_PRE_90_UPGRADE=1|0 (Windows)
APPLICATION_FOLDER
■ Description: This option specifies the application folder for NetBackup. The fully
qualified path to the base directory is required.
■ Applicable platforms: Windows only.
■ Default value: None.
■ Required: No
■ APPLICATION_FOLDER=C:\Program Files\Veritas
AUTHORIZATION_TOKEN
CA_CERTIFICATE_FINGERPRINT
CLIENT
■ Description: This option specifies the name that NetBackup uses to identify this
client host. The %COMPUTERNAME% value lets the local host provide the computer
name. If this value is used, it may be possible to use the same answer file on
all computers within a single primary server domain. The use of IP addresses
is not supported.
■ Applicable platforms: Windows only.
■ Default value: None.
■ Required: Yes.
■ CLIENT=client_name | %COMPUTERNAME%
CLIENT_NAME
■ Description: This option specifies the name that NetBackup uses to identify this
computer. The XLOCALHOSTX value lets the local host provide the computer
name. If this value is used, it may be possible to use the same answer file on
all computers within a single primary server domain. This value is added to the
bp.conf file.
If CLIENT_NAME is specified on upgrade, a check is made to validate that the
name that is provided in the answer file matches the value that is configured in
the bp.conf file.
■ Applicable platforms: UNIX and Linux only.
■ Default value: None.
■ Required: No
■ CLIENT_NAME=name | XLOCALHOSTX
DATABASE_USER
■ Description: This option specifies the user name of the account that owns the
NetBackup scale-out database instance.
This user must already exist on the system. The DATABASE_USER cannot be root.
The DATABASE_USER cannot be an account with access to the sudo utility. If the
specification resolves to root, the installation fails. If the SERVICE_USER defined
previously is not root, you can specify SAME_AS_SERVICE_USER. Otherwise,
specify a non-root user account name.
■ Applicable platforms: Linux
■ Default value: SAME_AS_SERVICE_USER
■ Required: Conditional.
This value is required if the service user is root. Additionally, this value is required
if DATABASE_USER does not exist in the bp.conf file and the configured
SERVICE_USER entry is root. If the value is provided and the DATABASE_USER
exists in bp.conf, this value must match the configured database user on the
machine.
■ DATABASE_USER = username | SAME_AS_SERVICE_USER
ECA_CERT_PATH
■ Description: This option specifies the path and the file name of the external
certificate file.
The ECA_CERT_PATH option is ignored on upgrade if ECA is already configured
on the host or if NBCA only is in use on the primary server.
■ Applicable platforms: All.
■ Default value: None.
■ Required: Review About security configuration considerations for details.
■ ECA_CERT_PATH=path_and_file_name
ECA_CERT_STORE
ECA_CRL_CHECK_LEVEL
■ Description: This option specifies the CRL mode. Supported values are:
■ USE_CDP: Use the CRL defined in the certificate.
ECA_CRL_PATH
■ Description: This option specifies the path and the file name of the CRL
associated with the external CA certificate.
The ECA_CERT_PATH option is ignored on upgrade if ECA is already configured
on the host or if NBCA only is in use on the primary server.
■ Applicable platforms: All.
■ Default value: None.
■ Required: Only when ECA_CRL_CHECK_LEVEL=USE_PATH is specified.
■ ECA_CRL_PATH=path
ECA_KEY_PASSPHRASEFILE
■ Description: This option specifies the path and the file name of the file that
contains the passphrase to access the keystore.
The ECA_CERT_PATH option is ignored on upgrade if ECA is already configured
on the host or if NBCA only is in use on the primary server.
■ Applicable platforms: All.
■ Default value: None.
■ Required: No
■ ECA_KEY_PASSPHRASEFILE=path/filename
ECA_PRIVATE_KEY_PATH
■ Description: This option specifies the path and the file name of the file
representing the private key.
The ECA_CERT_PATH option is ignored on upgrade if ECA is already configured
on the host or if NBCA only is in use on the primary server.
■ Applicable platforms: All.
■ Default value: None.
■ Required: Review About security configuration considerations for details.
■ ECA_PRIVATE_KEY_PATH=path/filename
ECA_TRUST_STORE_PATH
■ Description: This option specifies the path and the file name of the file
representing the trust store location.
The ECA_CERT_PATH option is ignored on upgrade if ECA is already configured
on the host or if NBCA only is in use on the primary server.
■ Applicable platforms: All.
■ Default value: None.
■ Required: Review About security configuration considerations for details.
■ ECA_TRUST_STORE_PATH=path/filename
IGNORE_MISSING_CATALOG_BACKUP
INCLUDE_JAVA_GUI_AND_JRE
■ Description: Used to determine how to handle the optional Java and JRE
components during install or upgrade. Supported values are:
■ INCLUDE: Include the Java GUI and JRE as part of the installation or upgrade.
■ EXCLUDE: Exclude the Java GUI and JRE. This option also removes all
previous versions of the Java GUI and the JRE if they are present on the
host.
■ MATCH: Match the existing configuration on the host. If you specify this option
on an initial installation, the components are not installed.
INCLUDE_VRTSPDDEU_CLIENT
■ Applicable platforms: Linux. Specifically, Red Hat Linux clients that are neither
pSeries nor zSeries.
■ Default value: MATCH
■ Required: No
■ INCLUDE_VRTSPDDEU_CLIENT = INCLUDE | EXCLUDE | MATCH
INSTALL_ITA_DATA_COLLECTOR
INSTALL_PATH
■ Description: This option specifies the location to install the NetBackup binaries.
Be aware that the INSTALL_PATH option is ignored on upgrade. This option
cannot be used to change the location of NetBackup during an upgrade. Only
the absolute path to a base directory is required for this option. The installer
automatically appends /openv.
■ Applicable platforms: UNIX and Linux only.
■ Default value: /usr
■ Required: No, the INSTALL_PATH option is ignored on upgrade.
■ INSTALL_PATH = path
LICENSE
■ Description: This option specifies the path of the license file to apply to the
primary server. For Linux, additional LICENSE lines may be added if more licenses
are to be applied. For Windows, use a single LICENSE line with multiple license
file paths separated with semicolons. This option only adds additional keys. Any
conflicting licenses are removed.
Reference 164
About the NetBackup answer file
Veritas recommends the use of your production license that is downloaded from
VEMS, for all upgrades. If you do not have access to your production license,
you can use one of the built-in non-downloaded licenses. Which license you
use depends on your version of NetBackup.
The evaluation license (EVALUATION) is only used during upgrades if the upgrade
is from NetBackup versions earlier than NetBackup 8.1.2. The evaluation license
is valid for 60 days. Alerts appear in the web UI immediately after upgrade,
indicating the number of days remaining in the evaluation.
The temporary license (TEMP_PRODUCTION) is used in upgrades of NetBackup
8.1.2 or later to NetBackup 10.3 or later. The temporary license is valid for 60
days. Alerts appear in the web UI immediately after upgrade, indicating the
number of days remaining before the temporary license expires.
Note: You cannot use the temporary production license when you upgrade
from a NetBackup version earlier than 8.1.2. Upgrades from versions earlier
than NetBackup 8.1.2 only support the production licenses that are
downloaded from VEMS or the evaluation license.
■ For upgrades from NetBackup 10.3 to later releases: No, provided there is
a valid license on the primary server. Not required for media servers and
clients.
More information is available:
https://www.veritas.com/support/en_US/article.100058779
■ LICENSE = TEMP_PRODUCTION | slf_filepath | EVALUATION
More information is available:
https://www.veritas.com/support/en_US/article.100058779
■ Return to Table A-2.
Reference 165
About the NetBackup answer file
MACHINE_ROLE
■ Description: This option specifies the NetBackup role to install and configure on
this computer. For upgrades, this value must match the configured role on the
computer.
■ Default value: None. Supported values are PRIMARY, MEDIA, and CLIENT.
■ Applicable platforms: UNIX and Linux only.
■ Required: No.
■ MACHINE_ROLE = PRIMARY | MEDIA | CLIENT
MEDIA_SERVER
■ Description: This option specifies that NetBackup may use the named host to
tunnel secure web requests for this client. A tunnel is required when
communication between the client and the NetBackup Web Service on the
primary server is blocked. This communication is required to obtain a host
certificate during the NetBackup installation or upgrade. You can have multiple
MEDIA_SERVER entries in the answer file.
MEDIASERVER
■ Description: This option specifies the name of the host this computer recognizes
as its media server. The use of IP addresses is not supported.
■ Applicable platforms: Windows only.
■ Default value: None.
■ Required: No.
■ MEDIASERVER=media_server_name
MERGE_SERVERS_LIST
■ Description: Merge the servers present in bp.conf on the primary with the server
list contained in this client's bp.conf.
Reference 166
About the NetBackup answer file
PRIMARYSERVER
■ Description: This option specifies the server name this computer recognizes as
the current NetBackup primary server. If this host is the primary server,
%COMPUTERNAME% can be used for the value. The use of IP addresses is not
supported. Additional primary servers can be specified with the
ADDITIONALSERVERS option.
PROCEED_WITH_INSTALL
■ Description: This option specifies the answer to two possible prompts during
the install or the upgrade of NetBackup. The first prompt determines if the install
or the upgrade proceeds after NetBackup passes critical preinstallation checks.
The user may receive a second prompt if there are potential disk space concerns.
In both cases, if YES, the install or upgrade proceeds to install the NetBackup
and media manager files on the file system. If NO, the install or the upgrade halts
and allows the user to make changes.
■ Applicable platforms: UNIX and Linux
■ Default value: None
■ Required: No
■ PROCEED_WITH_INSTALL = yes | no
RBAC_DOMAIN_NAME
■ Description: This option specifies the domain name of the principal that is
configured to have the role-based access control (RBAC) permissions for the
Administrator role.
■ Default value: None.
■ Applicable platforms: UNIX and Linux only.
■ Required: No
■ RBAC_DOMAIN_NAME = domain_name
RBAC_DOMAIN_TYPE
■ Description: This option specifies the domain type of the principal that is
configured to have the role-based access control (RBAC) permissions for the
Administrator role.
■ Applicable platforms: UNIX and Linux only.
■ Default value: None.
■ Required: No
■ RBAC_DOMAIN_TYPE = domain_type
RBAC_PRINCIPAL_NAME
■ Description: This option specifies the name of the principal that is configured to
have the role-based access control (RBAC) permissions for the Administrator
role. This user or the user group must already exist on the system.
■ Applicable platforms: UNIX and Linux only.
■ Default value: None.
■ Required: No
■ RBAC_PRINCIPAL_NAME = principal_name
RBAC_PRINCIPAL_TYPE
■ Description: This option specifies the type of the principal that is configured to
have the role-based access control (RBAC) permissions for the Administrator
role.
Reference 168
About the NetBackup answer file
SECURITY_CONFIGURATION
SERVER
■ Description: This option specifies the server name this computer recognizes as
the current NetBackup primary server. Additional SERVER= lines may be added
if there are other servers that should be recognized. In the case where multiple
SERVER= lines are present, the first occurrence is the primary server. These
entries are added to the bp.conf file.
■ Applicable platforms: UNIX and Linux only.
■ Default value: None.
■ Required: No.
■ SERVER=primary_server_name
SERVICES
NetBackup services are not started. Additional manual configuration steps may
be performed after the install or upgrade but before the NetBackup services are
started.
■ Applicable platforms: UNIX and Linux only.
■ Default value: YES
■ Required: No.
■ SERVICES=no
SERVICESTARTTYPE
■ Description: This option specifies if the NetBackup services are restarted after
the host server reboots.
■ Applicable platforms: Windows only.
■ Default value: Automatic
■ Required: No.
■ SERVICESTARTTYPE=Automatic | Manual
SERVICE_USER
■ Description: This option specifies the service user account is used to start most
of the NetBackup services or daemons on the primary server. Be aware of the
items shown:
■ Veritas recommends you do not use the root user as the service user.
■ Veritas recommends you do not use the nbwebsvc user as the service user.
■ The nbwebgrp group must be a secondary group of the service user.
■ Ownership of the /usr/openv directory changes to the new service user
account that you specify with this option.
■ Use the nbserviceusercmd --changeUser command to change this user
after installation.
■ For cluster servers, the service user and the service user ID must be same
on all cluster nodes.
■ If the SERVICE_USER value is provided in the answer file and it exists in the
bp.conf file, the values must match.
Reference 170
About the NetBackup answer file
START_JOB_DAEMONS
■ Description: This option specifies whether the NetBackup daemons that control
the execution of jobs should be started.
■ Applicable platforms: Linux only.
■ Default value: yes
■ Required: No.
■ START_JOB_DAEMONS=yes|no
STOP_NB_BEFORE_VCREDIST
STOP_NBU_PROCESSES
■ Description: This option specifies if the install process should stop any active
NetBackup processes automatically if detected. Be sure to confirm there are no
active NetBackup jobs and that all NetBackup databases are shut down before
installation or upgrade. Valid input values are 0 for don't stop, and 1 for stop.
■ Applicable platforms: Windows only.
Reference 171
About the NetBackup answer file
■ Default value: 0
■ Required: No.
■ STOP_NBU_PROCESSES = 0 | 1
VCREDIST_ATTEMPT_PREFERENCE
VCREDIST_RESTART_PREFERENCE
■ Description: This option determines how the NetBackup setup proceeds if the
Visual C++ run-time libraries were updated and a restart is required to complete
the operation. If the option is set to STOP, the setup halts. If the option is set to
PROCEED, NetBackup continues the setup but does not restart the computer.
Veritas recommends performing a required restart as soon as possible.
■ Applicable platforms: Windows only.
■ Default value: STOP
■ Required: No
■ VCREDIST_RESTART_PREFERENCE=PROCEED|STOP
VNETD_PORT
■ Description: This option specifies the port NetBackup's vnetd process uses.
■ Applicable platforms: Windows only.
■ Default value: 13724
■ Required: No.
Reference 172
About the NetBackup answer file
■ VNETD_PORT=port_number
VXDBMS_POSTGRESQL_POOLER_ODBC_PORT
■ Description: This option specifies the port that the NetBackup scale-out database
connection pool service uses.
■ Applicable platforms: All.
■ Default value: 13787
■ Required: No.
If the value is provided for upgrade, it must match the current value that is stored
in the VXDBMS_POSTGRESQL_POOLER_ODBC_PORT field in vxdbms.conf.
■ VXDBMS_POSTGRESQL_POOLER_ODBC_PORT = port_number
WEBSVC_DOMAIN
■ Description: Use this option to associate the web server with Domain (Active
Directory) accounts. Provide the domain name in this field. If you plan to
associate the web server with local accounts, leave this field blank.
■ Applicable platforms: Windows only.
■ Default value: None.
■ Required: No.
■ WEBSVC_DOMAIN=domain_name
WEBSVC_GROUP
■ Description: This option specifies the group name of the account that the
NetBackup web server uses. This group must already exist on the system.
■ If the WEBSVC_GROUP value is provided in the answer file and it exists in the
bp.conf file, the values must match.
WEBSVC_PASSWORD_PLAIN
■ Description: This option specifies the password for the Windows WEBSVC_USER
account. If your websvc password contains any special characters (% ^ & < >
| ' ` , ; = ( ) ! " \ [ ] . * ?), add the appropriate escape characters
to the password. For example if the websvc password is abc% you must enter
abc%%.
Caution: This option places the password for this account in clear text and can
potentially be a security concern.
WEBSVC_USER
■ Description: This option specifies the user name of the account that the
NetBackup web server uses. This user must already exist on the system.
If the WEBSVC_USER value is provided in the answer file and it exists in the bp.conf
file, the values must match.
■ Applicable platforms: All.
■ Default value: nbwebsvc
■ Required: Linux primary servers, no. Windows primary servers, yes.
■ WEBSVC_USER=custom_user_account_name
■ Install the client type software on the primary server. Be sure to install all of the
client types that pertain to your NetBackup configuration.
As of NetBackup 10.5, no client software is populated in the client push install
and upgrade staging area. Follow the process that is shown for all client operating
systems.
See “Installing client type software on a primary server” on page 174.
■ Before you can push client software from the primary server, each client name
must be assigned to a NetBackup policy. Policies are created on the primary
server.
When you create a policy, you must identify the policy type, which indicates the
operating system on the clients that are assigned to that policy. Without a policy,
the remote installation (or push) fails because the primary server does not know
the operating system of the client.
For information on how to create NetBackup policies, refer to the NetBackup
Administrator's Guide, Volume I.
■ After the required policies are created, you can push client software from the
primary server to the clients.
4 Select all of the client types that you want to install and follow the installation
prompts.
Once the Data Collector is installed and configured, the Data Collector reports
NetBackup information to NetBackup IT Analytics Portal or Veritas Alta Analytics.
How NetBackup handles the Data Collector values in the answer file depends on
the NetBackup version and the current state of the NetBackup IT Analytics Data
Collector.
Upgrades
■ If the NetBackup IT Analytics Data Collector is installed and configured, the
answer file is always ignored. The NetBackup IT Analytics Data Collector handles
the upgrades.
■ For pre-10.1.1 versions of NetBackup, if the NetBackup IT Analytics Data
Collector is not installed, NetBackup always honor the value in the answer file.
If there is no value in the answer file, the NetBackup IT Analytics Data Collector
is installed by default.
■ For NetBackup versions 10.1.1 and later, if the NetBackup IT Analytics Data
Collector is not installed, NetBackup never installs NetBackup IT Analytics Data
Collector, regardless of the values in the answer file.
■ For NetBackup versions 10.1.1 and later, if the NetBackup IT Analytics Data
Collector is installed but not configured, NetBackup always upgrades the binaries
to the latest version, regardless of the values in the answer file. This behavior
insures the binaries are always current.
■ Regardless of version, the value NO in the answer file does not uninstall the
NetBackup IT Analytics Data Collector. You must manually uninstall the
NetBackup IT Analytics Data Collector.
References
For additional information:
■ See Installing the Data Collector software in the NetBackup IT Analytics Data
Collector Installation Guide.
■ See Clustering Data Collectors with VCS and Veritas NetBackup in NetBackup
IT Analytics Data Collector Notes and Troubleshooting guide.
You may need to manually install the Data Collector if it fails to install during the
NetBackup install or upgrade. A failure to install the Data Collector does not cause
the entire NetBackup primary server installation or upgrade to fail. If you don't plan
to use the Data Collector, you may want to uninstall it.
The steps that are shown do not configure the Data Collector to connect with any
portal. These steps only install the Data Collector. The Data Collector is configured
after the NetBackup primary server connects with Veritas Alta Analytics or
NetBackup IT Analytics Portal.
More information about how to configure the Data Collector is available.
See “Manually configure the NetBackup IT Analytics Data Collector” on page 177.
To manually install the Data Collector on a Linux primary server:
1 Copy /catalog/anb/ita_dc.tar.gz to a temporary location.
2 Extract the ita_dc.tar.gz tarball in that temporary location.
3 Run temporary_location/dc_installer -i /usr/openv -n
To manually install the Data Collector on a Windows primary server:
1 Locate the installation media kit and navigate to the x64/ITA_DC folder.
2 Run silentinstall.cmd /INSTALL_PATH:NetBackup_install_path
/INSTALL_TYPE:INSTALL /REMOVE_NON_OEM_DIR:Y
SET DATACOLLECTOR_NAME=name_of_the_data_collector
SET DATACOLLECTOR_PASSCODE=passcode_for_the_data_collector
SET DATARECEIVER_URL=data_receiver_URL
SET DATACOLLECTOR_KEY_FILE_PATH=path_to_the_key_file
SET HTTP_PROXY_CONF=N
SET PROXY_HTTP_URL=
SET PROXY_HTTP_PORT=
SET PROXY_HTTPS_URL=
SET PROXY_HTTPS_PORT=
SET PROXY_USERID=
SET PROXY_PASSWORD=
SET PROXY_NOT_FOR=
2 Update the value for each field with appropriate data. A sample response file
is also available in the installer media in x64\ITA_DC\responsefile.cmd.
Reference 179
Manually configure the NetBackup IT Analytics Data Collector
"C:\ProgramData\Veritas\NetBackup IT Analytics\DC\configure.cmd"
\RESPFILE:response_file_path \INSTALL_TYPE:CONFIG
checkinstall.bat
If the Data Collector is configured with the Portal, the response is displayed
as SUCCESSFUL.
COLLECTOR_NAME=name_of_the_data_collector
COLLECTOR_PASSCODE=passcode_for_the_data_collector
DR_URL=data_receiver_URL
COLLECTOR_KEY_PATH=path_to_the_key_file
HTTP_PROXY_CONF=N
HTTP_PROXY_ADDRESS=
HTTP_PROXY_PORT=
HTTPS_PROXY_ADDRESS=
HTTPS_PROXY_PORT=
PROXY_USERNAME=
PROXY_PASSWORD=
PROXY_EXCLUDE=
/usr/openv/analyticscollector/installer/dc_installer.sh -c
responsefile_path
/usr/openv/analyticscollector/mbs/bin/aptare_agent start
/usr/openv/analyticscollector/mbs/bin/aptare_agent stop
/usr/openv/analyticscollector/mbs/bin/aptare_agent status
On Windows: Review the status of Aptare Agent, Aptare Kafka, and Aptare
Zookeeper services on the Windows service panel.
The upgrade is required to ensure that the Data Collector version is the same as
the NetBackup IT Analytics Portal version.
WMC_HEAP
WMC_METASPACE
WMC_NEW_RATIO
WMC_SURVIVOR_RATIO
WMC_GC_CONFIG
WMC_HEAP_DUMP_CONFIG
Refer to the JVM documentation from Oracle for more information on the
variables and their appropriate ranges.
3 Restart the web service to apply the configuration changes.
grant the Administrator role permissions to the user or the user group that you
specify in the /tmp/NBInstallAnswer.conf file.
Note: RBAC bootstrapping provides access to all objects for the specified user or
user group, even if previously the user or the user group had restricted access to
certain objects. For example, the existing user Tester1 was assigned the Default
VMware Administrator role. If Tester 1 is specified for RBAC bootstrapping, Tester1
is assigned the Administrator role.
After installation or upgrade, you can run the bpnbaz -AddRBACPrincipal command
standalone on both Windows and Linux platforms to assign RBAC permissions.
The command is available only on the primary server. For more information about
this command, see the NetBackup Commands Reference Guide.
RBAC_DOMAIN_NAME = domain_name
RBAC_PRINCIPAL_NAME = principal_name
Be aware that RBAC_DOMAIN_TYPE supports the values shown: NT, VX, UNIXPWD,
LDAP.
RBAC bootstrapping is not performed if all the entries are empty or missing. In this
case, the message Answer file did not contain any RBAC entries is posted
in the install trace file. The install process always continues whether the RBAC
bootstrapping is successful or not. The audit records are created under the
SEC_CONFIG category.
The installer also displays this message if the user or the user group already exists
with the Administrator RBAC role.
If one or more RBAC entries exist in the answer file, but a required answer file entry
is missing, the installer displays the following message:
Warning: Unable to configure the RBAC permissions. One or more
required fields are missing in /tmp/NBInstallAnswer.conf.
If there are other issues with the RBAC Bootstrapping, the installer displays the
following message:
Warning: Failed to configure the RBAC permissions for principal_name.
Refer to logs in /usr/openv/netbackup/logs/admin for more information.
If RBAC bootstrapping is successful but auditing fails, the install displays the
following message:
After the installation or upgrade completes, the specified user or user group is
assigned the Administrator role with its corresponding RBAC access permissions.
The user can then access APIs and the Web UI.
Caution: If at any time after the upgrade the mode changes from Node scope to
Vserver aware, you must perform the additional steps. Failure to perform the
additional steps places your data at risk.
Note: Once a media server detects Vserver aware mode, no further backup activities
are performed on any other media server running any earlier releases of NetBackup.
If you change from Node scope mode to Vserver aware mode, you must do the
following:
Additional changes for Node scope mode to Vserver aware mode
1 Enable the Vserver aware mode on the cluster by disabling node-scope-mode.
2 If there are tape devices attached to the cluster nodes, you must reconfigure
them. Configure the tape devices to use the cluster-management logical
interface (LIF) as the NDMP host for the device configuration. NetBackup does
not support use of node name for device configuration.
See the NetBackup NAS Administrator's Guide for additional information.
Reference 186
Additional post-upgrade steps for NetApp clusters
5 Update or replace any storage units that use the node names of the cluster to
use the cluster LIF.
6 Update or replace any existing policies that back up the cluster.
You must use either the Data LIF or the Cluster-management LIF as the client
name. NetBackup does not support the use of the node name for the client
name. The backup selections may also need to be modified.
7 Add an intercluster management LIF for each node that does not host a cluster
management LIF.
The NetApp cluster requires this activity to perform NDMP 3 way or NDMP
Remote backups. Without these LIFs, all 3 way or remote backups from the
volumes that are not hosted on the same node as the cluster management LIF
fail.
8 To restore, verify, or duplicate the old images, you may have to use alternate
read host.
Reference 187
Using NetApp disk arrays with Replication Director
Once the command runs successfully, the output of the nbemmcmd should look
similar to the following:
8.x and later 1.1 Provides 7-mode support One primary server supports MS-Windows, Standard,
for all NetBackup many OCUM servers. NDMP, VMware, Oracle
Replication Director
The plug-in must be installed on
features.
the OnCommand Unified
Manager (OCUM) server.
1.1 P1 Provides 7-mode support One primary server supports MS-Windows, Standard,
for all NetBackup many OCUM servers. NDMP, VMware, Oracle
Replication Director
features.
2.0 Provides cDOT support. One primary server supports MS-Windows, Standard,
many OCUM servers. NDMP, VMware, Oracle
Note: You must upgrade the entire NetBackup environment before upgrading the
plug-in. Upgrade all primary servers, media servers, clients, and any hosts which
communicate with the plug-in.
Reference 189
Using NetApp disk arrays with Replication Director
NFS/CIFS
iSCSI/FC
iSCSI/FC
NetApp OnCommand Unified Manager
NBUPlugin for 7-mode
SnapMirror
SnapVault
NFS/CIFS
NBUPlugin for cDOT
(Linux or Windows)
Cluster 1 Cluster 2
SnapMirror
SVM1 SVM1
SnapVault
SVM2 SVM2
SVM3 SVM3
C-mode Secondary
Operating ■ For a complete list of compatible UNIX and Linux operating systems, refer to the
System Software Compatibility List (SCL) at the following website:
http://www.netbackup.com/compatibility
https://sort.veritas.com/netbackup
Memory Use the information that is shown to correctly size your server:
■ The SORT website. See “About Veritas Services and Operations Readiness Tools”
on page 29.
■ General details on how to size your NetBackup environment. See “Size guidance for
the NetBackup primary server and domain” on page 208.
■ Detailed information about planning and tuning your NetBackup environment are
available. These details are found in the NetBackup Backup Planning and Performance
Tuning Guide.
Disk space ■ The exact amount of space that is required depends on the hardware platform. More
information about this topic is available.
NetBackup Release Notes for 10.5
■ NetBackup catalogs contain information about your backups that become larger as
you use the product. The disk space that the catalogs require depends primarily on
the following aspects of your backup configuration:
■ The number of files that are backed up.
■ The frequency of your backups.
■ The amount of time that you set to retain your backup data.
If space is an issue, you can install NetBackup on an alternate file system. The installation
lets you select an alternate install location, and creates the appropriate link from
/usr/openv.
Note: The value for disk space is for initial installation only. The NetBackup catalog
requires considerably more space once the primary server is placed in a production
environment.
Reference 193
Upgrade requirements for UNIX and Linux
General ■ Ensure that the gzip and the gunzip commands are installed on the local system.
requirements The directories where these commands are installed must be part of the root user’s
path environment variable setting.
■ All NetBackup installation ESD images, appropriate licenses, and the root password
for all servers.
■ A server of a supported hardware type that runs a supported version of its operating
system (with applicable patches), adequate disk space, and supported peripherals.
For details on these requirements, refer to the NetBackup Release Notes for 10.5.
■ All NetBackup servers must recognize and be recognizable by their client systems.
In some environments, this means that each must be defined in the other’s
/etc/hosts file. Other environments may use the Network Information Service (NIS)
or Domain Name Service (DNS).
■ The minimum screen resolution configuration is 1024x768, 256 colors.
Clustered ■ Ensure that each node in the NetBackup cluster can run the ssh command or its
systems equivalent. The root user must be able to perform a remote logon to each node in
the cluster without entering a password. This remote logon is necessary for installation
and configuration of the NetBackup server and any NetBackup agents and options.
After installation and configuration are complete, it is no longer required.
■ You must install, configure, and start the cluster framework before you install
NetBackup.
■ You must have defined a virtual name using DNS, NIS, or the /etc/hosts file. The
IP address is defined at the same time. (The virtual name is a label for the IP address.)
■ Begin the upgrade from the active node, and then upgrade the inactive nodes.
NFS Veritas does not support installation of NetBackup in an NFS-mounted directory. File
compatibility locking in NFS-mounted file systems can be unreliable.
Linux Before NetBackup installation, confirm the files that are shown are present and installed
if necessary. If any file is not present, install the one provided by your operating system.
■ libnsl.so.1
■ libXtst
Red Hat Linux For Red Hat Linux, NetBackup requires server networking.
Reference 194
Upgrade requirements for UNIX and Linux
Other backup Veritas recommends that you remove any other vendor backup software currently
software configured on your system before you install this product. Other vendor backup software
can negatively affect how NetBackup installs and functions.
Web Services Beginning with NetBackup 8.0, the NetBackup primary server includes a configured
Tomcat web server to support critical backup operations. This web server operates under
user account elements with limited privileges. These user account elements must be
available on each primary server (or each node of a clustered primary server). You must
create these required account elements before installation. More information is available:
See “NetBackup primary server web server user and group creation” on page 137.
Note: Veritas recommends that you save the details of the user account that you use
for the NetBackup Web Services. A primary server recovery requires the same NetBackup
Web Services user account and credentials that were used when the NetBackup catalog
was backed up.
Note: If the NetBackup PBX is running in secure mode, please add the web service
user as authorized user in PBX. More information about determining PBX mode and how
to correctly add users is available.
http://www.veritas.com/docs/000115774
By default, the UNIX installation script attempts to associate the web server with user
account nbwebsvc and group account nbwebgrp. You can override these default values
with the NetBackup installation answer file. You must populate the NetBackup installation
answer file on the target host before you start the UNIX installation script. Populate the
NetBackup installation answer file with custom web server account names as shown.
2 Open the file /tmp/NBInstallAnswer.conf with your preferred text editor. Create the
file if it does not exist.
3 Override the default web server user account name by adding the line shown:
WEBSVC_USER=custom_user_account_name
4 Override the default web server group account name by adding the line shown:
WEBSVC_GROUP=custom_group_account_name
Caution: Veritas supports moving the 10.5 catalog with the nbdb_move command
to a non-default location on a Windows cluster after installation or upgrade. Before
any upgrades, however, you must move the 10.5 catalog back to the default location
for the upgrade to succeed. Do not attempt a 10.5 upgrade if the catalog is not in
the default location. You primary server is rendered unusable if you fail to move
the database back to the default location before upgrade. More information about
the nbdb_move is available.
10.5 Commands Reference Guide
Operating ■ Make sure that you have applied the most current operating system patches and
system updates, including any security updates. If you are not certain that your operating
system is current, contact your operating system vendor and request the latest patches
and upgrades.
■ For a complete list of compatible Windows operating systems, refer to the Software
Compatibility List (SCL) at the following website:
http://www.netbackup.com/compatibility
Memory Use the information that is shown to correctly size your server:
■ The SORT website. See “About Veritas Services and Operations Readiness Tools”
on page 29.
■ General details on how to size your NetBackup environment. See “Size guidance for
the NetBackup primary server and domain” on page 208.
■ Detailed information about planning and tuning your NetBackup environment are
available. These details are found in the NetBackup Backup Planning and Performance
Tuning Guide.
Reference 196
Upgrade requirements for Windows and Windows clusters
Table A-7 10.5 requirements for Windows and Windows clusters (continued)
Note: The value for disk space is for initial installation only. The 10.5 catalog requires
considerably more space once the primary server is placed in a production environment.
General Make sure that you have all of the following items:
requirements
■ 10.5 installation ESD images
■ Appropriate license files
More information is available:
https://www.veritas.com/support/en_US/article.100058779
■ Administrator account and password for all servers
■ Screen resolution configured for at least 1024x768, 256 colors.
Reference 197
Upgrade requirements for Windows and Windows clusters
Table A-7 10.5 requirements for Windows and Windows clusters (continued)
Remote and In addition to all previously stated installation requirements, the following guidelines apply
cluster to remote installations and cluster installations:
installations
■ All nodes in the cluster must run the same operating system version, service pack
level, and 10.5 version. You cannot mix versions of server operating systems.
■ The installation account must have administrator privileges on all remote systems or
on all nodes in the cluster.
■ The Remote Registry service must be started on the remote system.
The 10.5 installer can enable and start the Remote Registry service on the remote
system. If the Remote Registry service is not started, the installation receives the
following error message:
Attempting to connect to server server_name failed with the
following error: Unable to connect to the remote system. One
possible cause for this is the absence of the Remote Registry
service. Please ensure this service is started on the remote
host and try again.
■ 10.5 virtual name and IP address
Have the virtual name and IP address for 10.5 available. You must provide this
information during installation.
■ Cluster support changes for media servers
You cannot perform a new installation of a clustered media server.
■ Windows Server Failover Clusters (WSFC)
■ The shared disk that the 10.5 Group uses must already be configured in the cluster
and online on the active node.
■ Install 10.5 from the node with the shared disk (that is, the active node).
■ Computer or host names cannot be longer than 15 characters.
■ Cluster server (VCS) clusters:
All 10.5 disk resources must be configured in Veritas Enterprise Administrator (VEA)
before you install 10.5.
■ Cluster node device configuration and upgrades
When you upgrade clusters, the ltid and the robotic daemons retrieve the device
configuration for a particular cluster node from the EMM database. The cluster node
name (provided by gethostname) stores or retrieves the device configuration in the
EMM database. The cluster node name is used when any updates are made to the
device configuration, including when ltid updates the drive status. The cluster node
name is only used to indicate where a device is connected. The 10.5 virtual name is
employed for other uses, such as the robot control host.
Table A-7 10.5 requirements for Windows and Windows clusters (continued)
Remote You must provide the names of the Remote Administration Console hosts during primary
Administration server installation.
Console host
names
10.5 Make sure that your network configuration allows all servers and clients to recognize and
communication communicate with one another.
Generally, if you can reach the clients from a server by using the ping command, the
setup works with 10.5.
■ 10.5 services and port numbers must be the same across the network.
■ Veritas suggests that you use the default port settings for 10.5 services and Internet
service ports. If you modify the port numbers, they must be the same for all primary
servers, media servers, and clients. The port entries are in the following file:
%SYSTEMROOT%\system32\drivers\etc\services. To change the default
settings, you must perform a custom installation of 10.5 or manually edit the services
file.
CIFS-mounted Veritas does not support installation of 10.5 in a CIFS-mounted directory. File locking in
file systems CIFS-mounted file systems can be unreliable.
Storage devices Devices such as robots and standalone tape drives must be installed according to the
manufacturers’ instructions and recognized by the Windows software.
Server names When you are prompted for server names, always enter the appropriate host names. Do
not enter IP addresses.
Mixed versions Make sure to install 10.5 servers with a release level that is at least equal to the latest
client version that you plan to use. Earlier versions of server software can encounter
problems with later versions of client software.
Other backup Remove any other vendor’s backup software currently configured on your system. The
software backup software of another vendor can negatively affect how 10.5 installs and functions.
Reference 199
Upgrade requirements for Windows and Windows clusters
Table A-7 10.5 requirements for Windows and Windows clusters (continued)
Web Services Beginning with NetBackup 8.0, the NetBackup primary server includes a configured
Tomcat web server to support critical backup operations. This web server operates under
user account elements with limited privileges. These user account elements must be
available on each primary server (or each node of a clustered primary server). More
information is available:
See “NetBackup primary server web server user and group creation” on page 137.
Note: Veritas recommends that you save the details of the user account that you use
for the 10.5 Web Services. A primary server recovery requires the same 10.5 Web
Services user account and credentials that were used when the 10.5 catalog was backed
up.
Note: If the 10.5 PBX is running in secure mode, please add the web service user as
authorized user in PBX. More information about determining PBX mode and how to
correctly add users is available.
http://www.veritas.com/docs/000115774
https://www.veritas.com/support/en_US/article.000127129
In some cases, if you use a NetBackup Certificate Authority, the installer requires an
authorization token to successfully deploy security certificates. More information is
available about the details on authorization tokens and their role in generation of security
certificates.
https://www.veritas.com/support/en_US/article.000127129
Reference 200
Requirements for Windows cluster upgrades
Table A-7 10.5 requirements for Windows and Windows clusters (continued)
External For primary servers (including cluster): The configuration of an external certificate authority
certificate is a post-installation activity.
authority
For media servers and clients: You can configure the ECA during the install procedure
or after the installation completes. More information about post-installation configuration
is available:
https://www.veritas.com/support/en_US/article.100044300
For more information, see the 10.5 Security and Encryption Guide and refer to the chapter
on external CA and external certificates.
Item Requirement
Server operating system Make sure that you have applied the most current operating
system patches and updates, including any security updates.
If you are not certain that your operating system is current,
contact your operating system vendor and request the latest
patches and upgrades.
■ http://www.netbackup.com/compatibility
■ https://sort.veritas.com/netbackup
Item Requirement
NetBackup virtual name and Have the virtual name and IP address for NetBackup
IP address available. You must provide this information during
installation.
Operating system on nodes All clustered nodes must use the same operating system
version, service pack level, and NetBackup version. You
cannot run mixed server versions in a clustered environment.
Cluster support changes for Clustered media servers are not supported.
media servers
Windows Server Failover Make sure that you have applied the most current operating
Clusters (WSFC) system patches and updates, including any security updates.
If you are not certain that your operating system is current,
contact your operating system vendor and request the latest
patches and upgrades.
■ http://www.netbackup.com/compatibility
■ https://sort.veritas.com/netbackup
Cluster Server (VCS) clusters ■ All NetBackup disk resources must be configured in
Veritas Enterprise Administrator (VEA) before you install
NetBackup.
■ You must take the VCS NetBackup resource offline before
you begin the install or the upgrade.
Note: Make sure that shared disk and IP resources are
online during the install or the upgrade on active node.
The steps required to migrate all NetBackup resources and decommission a media
server is covered in depth in the NetBackup Administrator's Guide, Volume I. Please
see the About decommissioning a media server topic in the NetBackup
Administrator's Guide, Volume I.
READ_BUFFER_SIZE
WRITE_BUFFER_SIZE
4 Click Save.
Reference 203
Upgrading clients after servers are upgraded
Use the commands shown to update the read and write buffer size from the
command line
1 nbdevconfig -getconfig -stype storage_server_type -storage_server
storage_server_name -configlist filename
2 Update the value of the parameters shown. Enter these values in bytes:
READ_BUFFER_SIZE
WRITE_BUFFER_SIZE
Note: Be aware you cannot use the update_clients installation script to push
NetBackup 8.2 or later clients. You must use VxUpdate.
The update_clients installation script can determine the full client list that is
configured on the server. When it is run without any parameters, it attempts to
update all clients (as determined by
/usr/openv/netbackup/bin/admincmd/bpplclients). If you do not want to
upgrade all clients, you can specify a subset of clients. Use the hardware type and
operating system parameters or use the -ClientList parameter.
You can run update_clients from a media server. The -ClientList parameter
is required in this situation. The script lets you maintain a media server and a set
of clients at an earlier release level than the primary server. Doing so requires the
informed use of the update_clients -ClientList command on a primary server
and a media server to avoid unwanted client upgrades.
For clustered environments, you can push client software only from the active node.
Note: Additional steps are required to deploy clients in a secure environment where
the clients do not have direct connectivity to the primary server. More information
on this topic is available. See the topic on deploying certificates on clients without
connectivity to the primary server in the NetBackup Security and Encryption Guide.
Reference 204
Upgrading clients after servers are upgraded
During a client upgrade, the new client files are written to a directory in /tmp on the
client. This directory must have sufficient space to temporarily store the new client
files to ensure a successful upgrade. If sufficient space is not available, a status
message informs you that the upgrade script could not write to the location in the
/tmp directory. To resolve this issue, allocate more space to the /tmp directory and
perform the upgrade procedure again. The temporary directory is removed when
the upgrade is complete.
To upgrade clients after you have upgraded servers
1 Use one of the following methods to start the installation script:
ESD images (downloaded ■ Navigate to the location where the installation images
files) reside.
■ Enter the following command:
./install
Native install tools NetBackup supports the install and upgrade of the UNIX
and Linux client binaries with native installers. More
information is available.
The client binaries represent the operating system versions where the binaries
were compiled. The binaries typically function perfectly on later versions of the
operating system. For example, Solaris 10 binaries are also used on the Solaris
11 level of the operating system.
3 Select the client type that you want to load and follow the prompts to load that
client type. Repeat as necessary until all desired client types have been loaded.
Make sure that you load the software for all of the UNIX client types that you
intend to push to from this server. Otherwise, you cannot add these client types
to the NetBackup policy configuration.
Reference 205
Upgrading clients after servers are upgraded
4 As a root user on the NetBackup primary server, enter the following command
to see whether bprd is running:
/usr/openv/netbackup/bin/bpps
5 Enter the following command to make sure that backups or restores are not in
progress:
/usr/openv/netbackup/bin/admincmd/bpdbjobs
cd /usr/openv/netbackup/bin/admincmd
■ Use the bpplclients command to create a file that contains a list of clients
currently configured in the NetBackup database. The options to use on this
command differ depending on whether you push from a primary server or
from a media server, as follows:
file Name of the file to contain the list of unique clients. If no clients
have been configured in the NetBackup database, the file is
empty.
hardware os client
Type either y or n.
Press Enter.
Be aware if you press Ctrl+C, this action requires you to rerun the installation
or continue with the installation without the required security components. If
these security components are absent, backups and restores fail.
If a certificate authority certificate is found, you receive the message shown:
If you leave the authorization token blank, you receive the message shown:
11 After all servers and clients are updated, start the bprd daemon as the root
user on the primary server by entering the following command:
/usr/openv/netbackup/bin/initbprd
The /C switch is critical as it lets the operation proceed despite any failures.
Without this switch, the operation stops if there is any failure.
and storage targets that are properly sized with the necessary CPU, memory,
network bandwidth, and disk I/O to support the backup workloads. It is also
important to consider whether the same workloads require duplication or
replication to a DR location. Sizing the media servers and storage targets to
accommodate those secondary options is crucial. In summary, Veritas
recommends that you deploy properly sized media servers and storage targets,
while keeping the number less than 50 per domain.
■ The number of jobs must not exceed one job per second per client, but it is
possible to submit multiple jobs per second, each sent from a different client.
Each backup client has the "one job per second per client" limit, so multiple
clients may run in parallel.
■ Computing resources such as CPU and memory affect how well the primary
server scales.
To accommodate the processing of the metadata streams from media servers, it
is critical that the primary server has the requisite amount of system resources. A
media server sends metadata about the files it has backed up to the primary server.
This metadata is batched and sent periodically. The batch size, which is determined
by the tuning parameter MAX_ENTRIES_PER_ADD, has significant effect on primary
server performance, especially for backup images that contain many small files.
For additional information about batch size for sending metadata to the NetBackup
catalog, see the NetBackup Backup Planning and Performance Tuning Guide.
The primary server must then process each of these metadata message payloads.
Each payload requires an operating system process, each of which consumes
system resources. The consumed system resources are disk capacity, CPU cycles,
memory capacity, network bandwidth, and disk I/O.
Table A-9 provides additional information.
8 128 GB 20
16 256 GB 100
*Veritas
recommends that you limit the number of media servers to less than 50
media servers per domain.
Additional recommendations about processor and memory requirements are
available.
Reference 210
Size guidance for the NetBackup primary server and domain