NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (11.0)
  1. Introduction
    1.  
      About the NetBackup 11.0 Upgrade Guide
    2.  
      Available NetBackup upgrade methods
    3. About changes in NetBackup 11.0
      1.  
        Ansible supported playbooks for NetBackup
      2.  
        Client push staging area no longer populated
      3.  
        VRTSpddei.rpm no longer delivered in NetBackup 10.5
      4.  
        About binaries installed on primary and media servers
      5.  
        License file required for upgrade
      6.  
        Windows primary server upgrades are slowed if a large number of files are in the installation directory
      7.  
        About NetBackup database changes
      8.  
        NetBackup Administration Console and JRE installation optional for some computers
      9.  
        Logging directory permissions require reset on rollback
      10.  
        External certificate authority certificates supported in NetBackup 8.2 and later
    4.  
      About Cohesity Usage Insights
    5.  
      Best practices for Cohesity Usage Insights
  2. Planning for an upgrade
    1. General upgrade planning information
      1.  
        About planning a NetBackup 11.0 upgrade
      2.  
        How to plan for an upgrade to NetBackup 11.0
      3.  
        Legacy logging directory security update
      4.  
        Unified logging security update
      5.  
        Notifications, Messages, and Resiliency configuration information are not upgraded
      6.  
        Known catalog backup limitation
      7.  
        About security certificates for NetBackup hosts
      8.  
        About automatic file changes from an upgrade
      9.  
        Reduce the job database size before upgrade
      10.  
        Known SUSE Linux primary server upgrade issue
    2.  
      Performance and tuning considerations
    3. About upgrade tools
      1.  
        About Cohesity Services and Operations Readiness Tools
      2.  
        Recommended SORT procedures for upgrades
      3.  
        About the NetBackup preinstall checker
      4.  
        About the NetBackup database analyzer tool
    4. Upgrade operational notes and limitations
      1.  
        Minimum operating system versions
      2.  
        Windows compiler and security requirements for NetBackup 11.0 and later upgrade
      3.  
        Creating the user account to support the NetBackup web server
      4.  
        About NetBackup 11.0 support for Fibre Transport Media Server with RHEL 7.5 and later
      5.  
        MSDP changes in NetBackup 8.1
      6.  
        Potential required changes for NetApp clusters
      7.  
        Errors when Bare Metal Restore information is replicated using Auto Image Replication
      8.  
        Upgrade issue with pre-8.1 clients and 8.1 or later media servers
  3. Primary server upgrade
    1.  
      About primary server upgrades
    2.  
      Preinstall procedure for upgrading to NetBackup 11.0
    3.  
      Performing local, remote, or clustered server upgrades on Windows systems
    4.  
      Performing silent upgrades on Windows systems
    5.  
      Upgrading Linux server software to NetBackup 11.0
    6.  
      Silently upgrading NetBackup primary server software on Linux
    7.  
      Post-install procedure for upgrading to NetBackup 11.0
    8.  
      About NetBackup startup and shutdown scripts
    9.  
      Completing your system update after an upgrade
  4. Media server upgrade
    1.  
      Preinstall procedure for upgrading media servers to NetBackup 11.0
    2.  
      Upgrading NetBackup media servers to NetBackup 11.0
    3.  
      Silently upgrading NetBackup media server software on Linux
  5. MSDP upgrade for NetBackup
    1.  
      MSDP upgrade considerations for NetBackup 8.1
    2.  
      About MSDP rolling data conversion
    3.  
      About MSDP fingerprinting algorithm changes
  6. Client upgrade
    1.  
      About client upgrades
    2.  
      Preinstall procedure for upgrading clients to NetBackup 11.0
    3.  
      Upgrading UNIX and Linux clients with the NetBackup upgrade script
    4.  
      Upgrade of the UNIX and Linux client binaries with native installers
  7. NetBackup Deployment Management with VxUpdate
    1.  
      About VxUpdate
    2.  
      Commands used in VxUpdate
    3.  
      Repository management
    4.  
      Deployment policy management
    5.  
      Manually initiating upgrades from the primary server using VxUpdate
    6.  
      Manually initiating upgrades from the media server or client using VxUpdate
    7.  
      Deployment job status
    8.  
      EEB management view
  8. Appendix A. Reference
    1.  
      NetBackup primary server web server user and group creation
    2.  
      NetBackup database user
    3.  
      Generate a certificate on the inactive nodes of a clustered primary server
    4.  
      About the NetBackup Java Runtime Environment
    5.  
      Add or remove Java components after upgrade
    6.  
      About the NetBackup web user interface
    7.  
      About the NetBackup answer file
    8. About pushing client software from a primary server to clients
      1.  
        Installing client type software on a primary server
    9.  
      About the NetBackup IT Analytics Data Collector
    10.  
      Manually install or uninstall NetBackup IT Analytics Data Collector binaries
    11.  
      Manually configure the NetBackup IT Analytics Data Collector
    12.  
      Manually upgrading the NetBackup IT Analytics Data Collector
    13.  
      Persistent Java Virtual Machine options
    14.  
      About RBAC bootstrapping
    15.  
      About NetBackup software availability
    16.  
      Additional post-upgrade steps for NetApp clusters
    17.  
      Using NetApp disk arrays with Replication Director
    18.  
      About compatibility between NetBackup versions
    19.  
      Upgrade requirements for UNIX and Linux
    20.  
      Upgrade requirements for Windows and Windows clusters
    21.  
      Requirements for Windows cluster upgrades
    22.  
      Removing a clustered media server by migrating all data to a new media server
    23.  
      Post upgrade procedures for Amazon cloud storage servers
    24.  
      Upgrading clients after servers are upgraded
    25.  
      Upgrade failure rollback steps
    26.  
      Size guidance for the NetBackup primary server and domain

Available NetBackup upgrade methods

Table: UNIX and Linux upgrade and EEB and Table: Windows upgrade and EEB provide details on the ways in which you can upgrade NetBackup. To better understand which upgrade method is best for your environment, consider:

  • Interactive: Requires user input through the UI during the upgrade process.

  • Silent or native: Upgrades that use the Windows command files, or directly call the UNIX and Linux native package managers.

  • Push or remote: Includes options such as VxUpdate, Chef, and SCCM. Additionally, you can do a remote upgrade with Windows or use ssh or sftp with UNIX and Linux.

  • NetBackup supports the use of certain Ansible playbooks for upgrades. More information is available

    See Ansible supported playbooks for NetBackup.

Table: UNIX and Linux upgrade and EEB

Method

Primary

Media

Client

Interactive

See Upgrading Linux server software to NetBackup 11.0.

See Upgrading NetBackup media servers to NetBackup 11.0.

See About VxUpdate.

Yes. See the information about primary servers.

See About VxUpdate.

Silent or native

See Silently upgrading NetBackup primary server software on Linux.

See Silently upgrading NetBackup media server software on Linux.

See About VxUpdate.

See Upgrade of the UNIX and Linux client binaries with native installers.

See About VxUpdate.

Push or remote

Upgrade: No

EEB: Push upgrade of EEBs may work through 3rd party deployment tools.

See About VxUpdate.

See Upgrading clients after servers are upgraded.

See About VxUpdate.

Ansible playbooks

You can use NetBackup Ansible playbooks to upgrade NetBackup.

See Ansible supported playbooks for NetBackup.

You can use NetBackup Ansible playbooks to upgrade NetBackup.

See Ansible supported playbooks for NetBackup.

You can use NetBackup Ansible playbooks to upgrade NetBackup.

See Ansible supported playbooks for NetBackup.

Table: Windows upgrade and EEB

Method

Primary

Media

Client

Interactive

See Performing local, remote, or clustered server upgrades on Windows systems.

See Upgrading NetBackup media servers to NetBackup 11.0.

See About VxUpdate.

Yes. See the information about primary servers.

See About VxUpdate.

Silent

See Performing silent upgrades on Windows systems.

See Performing silent upgrades on Windows systems.

See About VxUpdate.

Yes. See the information about primary servers.

See About VxUpdate.

Push or remote

Upgrade: See Performing local, remote, or clustered server upgrades on Windows systems.

EEB: Push upgrade of EEBs may work through 3rd party deployment tools.

See Upgrading NetBackup media servers to NetBackup 11.0.

See About VxUpdate.

Yes. See the information about primary servers.

See About VxUpdate.

Ansible playbooks

You can use NetBackup Ansible playbooks to upgrade NetBackup.

See Ansible supported playbooks for NetBackup.

You can use NetBackup Ansible playbooks to upgrade NetBackup.

See Ansible supported playbooks for NetBackup.

You can use NetBackup Ansible playbooks to upgrade NetBackup.

See Ansible supported playbooks for NetBackup.

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 NetBackup. The deployment policy lets you configure and run deployment activities on a schedule or enable the client host owners to upgrade on demand. The use of VxUpdate for push or remote upgrades where possible is recommended.