NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup (10.1)
  1. Introduction
      About the NetBackup 10.1 Upgrade Guide
      Available NetBackup upgrade methods
    3. About changes in NetBackup 10.1
        Windows compiler and security requirements for NetBackup 9.1 and later installation and upgrade
        Java GUI and JRE installation optional for some computers
        Logging directory permissions require reset on rollback
        Upgrades from NetBackup and earlier are not supported
        External certificate authority certificates supported in NetBackup 8.2 and later
      About Veritas Usage Insights
      Best practices for Veritas Usage Insights
  2. Planning for an upgrade
    1. General upgrade planning information
        About planning a NetBackup 10.1 upgrade
        How to plan for an upgrade to NetBackup 10.1
        Legacy logging directory security update
        Notifications, Messages, and Resiliency configuration information are not upgraded
        Known catalog backup limitation
        About security certificates for NetBackup hosts
        About automatic file changes from an upgrade
        Reduce the job database size before upgrade
        Known SUSE Linux primary server upgrade issue
      Performance and tuning considerations
    3. About upgrade tools
        About Veritas Services and Operations Readiness Tools
        Recommended SORT procedures for upgrades
        About the NetBackup preinstall checker
    4. Upgrade operational notes and limitations
        Creating the user account to support the NetBackup web server
        About NetBackup 10.1 support for Fibre Transport Media Server with RHEL 7.5 and later
        MSDP changes in NetBackup 8.1
        Potential required changes for NetApp clusters
        Errors when Bare Metal Restore information is replicated using Auto Image Replication
        Upgrade issue with pre-8.1 clients and 8.1 or later media servers
  3. Primary server upgrade
      About primary server upgrades
      Preinstall procedure for upgrading to NetBackup 10.1
      Performing local, remote, or clustered server upgrades on Windows systems
      Performing silent upgrades on Windows systems
      Upgrading Linux server software to NetBackup 10.1
      Silently upgrading NetBackup primary server software on Linux
      Post-install procedure for upgrading to NetBackup 10.1
      About NetBackup startup and shutdown scripts
      Completing your system update after an upgrade
  4. Media server upgrade
      Upgrading NetBackup media servers to NetBackup 10.1
      Silently upgrading NetBackup media server software on Linux
  5. MSDP upgrade for NetBackup
      MSDP upgrade considerations for NetBackup 8.1
      About MSDP rolling data conversion
      About MSDP fingerprinting algorithm changes
  6. Client upgrade
      About client upgrades
      Upgrading UNIX and Linux clients with the NetBackup upgrade script
      Upgrade of the UNIX and Linux client binaries with native installers
  7. NetBackup Deployment Management with VxUpdate
      About VxUpdate
      Commands used in VxUpdate
      Repository management
      Deployment policy management
      Manually initiating upgrades from the primary server using VxUpdate
      Manually initiating upgrades from the media server or client using VxUpdate
      Deployment job status
  8. Appendix A. Reference
      NetBackup primary server web server user and group creation
      Generate a certificate on the inactive nodes of a clustered primary server
      About the NetBackup Java Runtime Environment
      Add or Remove Java GUI and JRE after upgrade
      About the NetBackup web user interface
      About the NetBackup answer file
      Persistent Java Virtual Machine options
      About RBAC bootstrapping
      About NetBackup software availability
      Additional post-upgrade steps for NetApp clusters
      Using NetApp disk arrays with Replication Director
      About compatibility between NetBackup versions
      Upgrade requirements for UNIX and Linux
      Upgrade requirements for Windows and Windows clusters
      Requirements for Windows cluster upgrades
      Removing a clustered media server by migrating all data to a new media server
      Post upgrade procedures for Amazon cloud storage servers
      Upgrading clients after servers are upgraded
      Upgrade failure rollback steps
      Size guidance for the NetBackup primary server and domain

Upgrade requirements for Windows and Windows clusters

Table: NetBackup requirements for Windows and Windows clusters describes the requirements to prepare your Windows systems for NetBackup installation. Use this table as a checklist to address each item.

For the most up-to-date information about installation requirements, Veritas recommends use of the SORT website. More information about SORT is available.

See About Veritas Services and Operations Readiness Tools.


Veritas supports moving the NetBackup 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 NetBackup catalog back to the default location for the upgrade to succeed. Do not attempt a NetBackup 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.

NetBackup Commands Reference Guide

Table: NetBackup requirements for Windows and Windows clusters





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.

  • For a complete list of compatible Windows operating systems, refer to the Software Compatibility List (SCL) at the following website:



Use the information that is shown to correctly size your server:

Disk space

  • An NTFS partition.

  • The exact amount of space that is required to accommodate the server software and the NetBackup catalogs depends on the hardware platform. More information about this topic is available.

    NetBackup Release Notes for 10.1

  • Upgrades require additional space on the primary drive, even if NetBackup is installed to an alterative location. The primary drive is the drive where Windows is installed.

    • For server upgrades Veritas requires 2.8 GB of free space on the primary Windows drive when you install NetBackup to an alternative drive location.

    • For client upgrades Veritas requires 1.7 GB of free space on the primary Windows drive when you install NetBackup to an alternative drive location.

  • 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.

  • Veritas recommends that you have a minimum available disk space of 5% in any Disk Storage Unit volume or file system.


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.


General requirements

Make sure that you have all of the following items:

  • NetBackup installation ESD images

  • Appropriate license keys

  • Administrator account and password for all servers

  • Screen resolution configured for at least 1024x768, 256 colors.


To install NetBackup on Windows 2012 R2, Windows 2012 UAC-enabled, Windows Server 2016, Windows 2019, and Windows 2022 environments, you must log on as the official administrator. Users that are assigned to the Administrators Group and are not the official administrator cannot install NetBackup in UAC-enabled environments. To allow users in the Administrators Group to install NetBackup, disable UAC.


Remote and cluster installations

In addition to all previously stated installation requirements, the following guidelines apply to remote installations and cluster installations:

  • All nodes in the cluster must run the same operating system version, service pack level, and NetBackup 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 source system (or primary node) must run Windows 2012/2012 R2/Windows 2016.

  • The destination PC (or clustered nodes) must have Windows 2012/2012 R2/Windows 2016.

  • The Remote Registry service must be started on the remote system.

    The NetBackup 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.

  • NetBackup virtual name and IP address

    Have the virtual name and IP address for NetBackup 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 NetBackup Group uses must already be configured in the cluster and online on the active node.

    • Install NetBackup 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 NetBackup disk resources must be configured in Veritas Enterprise Administrator (VEA) before you install NetBackup.

  • 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 NetBackup virtual name is employed for other uses, such as the robot control host.

More information about cluster requirements is available.

NetBackup Clustered Master Server Administrator's Guide


Remote Administration Console host names

You must provide the names of the Remote Administration Console hosts during primary server installation.

NetBackup communication

Make sure that your network configuration allows all servers and clients to recognize and communicate with one another.

Generally, if you can reach the clients from a server by using the ping command, the setup works with NetBackup.

  • NetBackup services and port numbers must be the same across the network.

  • Veritas suggests that you use the default port settings for NetBackup 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 NetBackup or manually edit the services file.

CIFS-mounted file systems

Veritas does not support installation of NetBackup in a CIFS-mounted directory. File locking in 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 NetBackup 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.

See About compatibility between NetBackup versions.


Installations on Windows 2012/2012 R2 Server Core/Windows 2016

You can only install NetBackup on these computers with the silent installation method.

See Performing silent upgrades on Windows systems.


Other backup software

Remove any other vendor's backup software currently configured on your system. The backup software of another vendor 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). More information is available:

See NetBackup primary server web server user and group creation.


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.


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.


CA Certificate fingerprint

(Conditional) For media servers and clients only:

If you use a NetBackup Certificate Authority, you must know the CA Certificate fingerprint of the primary server at time of installation. This requirement only applies if you use a NetBackup Certificate Authority. More information is available about the details on the CA Certificate fingerprint and its role in generation of security certificates.


Authorization Token

(Conditional) For media servers and clients only:

In some cases, 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.

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.


External certificate authority

For primary servers (including cluster): The configuration of an external certificate authority is a post-installation activity.

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:


Customer Registration Key for Veritas Usage Insights

Beginning with NetBackup 8.1.2, you must specify a Customer Registration Key for Veritas Usage Insights. More information about Veritas Usage Insights is available:

See About Veritas Usage Insights.

During install and upgrade to NetBackup 8.1.2, please allow the installer to copy the veritas_customer_registration_key.json file to its final destination. NetBackup can set the file permission and ownership correctly through this process. If you place the file onto your systems outside of the install or the upgrade process, the process may not work correctly.


Be aware that NetBackup does not support the short file name format (8.3 format) for the customer registration key file name.

See Upgrade requirements for UNIX and Linux.