NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup (10.1.1)
  1. Introduction
    1.  
      About the NetBackup 10.1.1 Upgrade Guide
    2.  
      Available NetBackup upgrade methods
    3. About changes in NetBackup 10.1.1
      1.  
        Windows compiler and security requirements for NetBackup 9.1 and later installation and upgrade
      2.  
        Java GUI and JRE installation optional for some computers
      3.  
        Logging directory permissions require reset on rollback
      4.  
        Upgrades from NetBackup 7.6.0.4 and earlier are not supported
      5.  
        External certificate authority certificates supported in NetBackup 8.2 and later
    4.  
      About Veritas Usage Insights
    5.  
      Best practices for Veritas Usage Insights
  2. Planning for an upgrade
    1. General upgrade planning information
      1.  
        About planning a NetBackup 10.1.1 upgrade
      2.  
        How to plan for an upgrade to NetBackup 10.1.1
      3.  
        Legacy logging directory security update
      4.  
        Notifications, Messages, and Resiliency configuration information are not upgraded
      5.  
        Known catalog backup limitation
      6.  
        About security certificates for NetBackup hosts
      7.  
        About automatic file changes from an upgrade
      8.  
        Reduce the job database size before upgrade
      9.  
        Known SUSE Linux primary server upgrade issue
    2.  
      Performance and tuning considerations
    3. About upgrade tools
      1.  
        About Veritas Services and Operations Readiness Tools
      2.  
        Recommended SORT procedures for upgrades
      3.  
        About the NetBackup preinstall checker
    4. Upgrade operational notes and limitations
      1.  
        Creating the user account to support the NetBackup web server
      2.  
        NetBackup IT Analytics Data Collector installed for NetBackup 10.1.1
      3.  
        About NetBackup 10.1.1 support for Fibre Transport Media Server with RHEL 7.5 and later
      4.  
        MSDP changes in NetBackup 8.1
      5.  
        Potential required changes for NetApp clusters
      6.  
        Errors when Bare Metal Restore information is replicated using Auto Image Replication
      7.  
        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 10.1.1
    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 10.1.1
    6.  
      Silently upgrading NetBackup primary server software on Linux
    7.  
      Post-install procedure for upgrading to NetBackup 10.1.1
    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 10.1.1
    2.  
      Upgrading NetBackup media servers to NetBackup 10.1.1
    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 10.1.1
    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. Appendix A. Reference
    1.  
      NetBackup primary server web server user and group creation
    2.  
      Generate a certificate on the inactive nodes of a clustered primary server
    3.  
      About the NetBackup Java Runtime Environment
    4.  
      Add or Remove Java GUI and JRE after upgrade
    5.  
      About the NetBackup web user interface
    6.  
      About the NetBackup answer file
    7.  
      Manual install or uninstall of the NetBackup IT Analytics Data Collector
    8.  
      Configure Data Collector manually for NetBackup
    9.  
      Persistent Java Virtual Machine options
    10.  
      About RBAC bootstrapping
    11.  
      About NetBackup software availability
    12.  
      Additional post-upgrade steps for NetApp clusters
    13.  
      Using NetApp disk arrays with Replication Director
    14.  
      About compatibility between NetBackup versions
    15.  
      Upgrade requirements for UNIX and Linux
    16.  
      Upgrade requirements for Windows and Windows clusters
    17.  
      Requirements for Windows cluster upgrades
    18.  
      Removing a clustered media server by migrating all data to a new media server
    19.  
      Post upgrade procedures for Amazon cloud storage servers
    20.  
      Upgrading clients after servers are upgraded
    21.  
      Upgrade failure rollback steps
    22.  
      Size guidance for the NetBackup primary server and domain

Manually initiating upgrades from the media server or client using VxUpdate

Manually initiate deployment jobs when you are logged into the media server or client locally and want to force an immediate update. You can either use a deployment policy to initiate an immediate upgrade or specify an upgrade without an associated policy. You can use the upgrade to update the NetBackup version or for other upgrades such as emergency binaries.

Among the reasons for a media server or a client initiated upgrade using VxUpdate is mission critical systems with specific maintenance windows. One example of these systems is database servers with limited available down time.

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.

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.

    • Create a policy on the primary server. Then run policy-based nbinstallcmd on the target client or media server.

    • Disable the external certificate on your primary server before starting the non-policy-based upgrade on the target host. You may turn on the external certificate after the upgrade completes successfully.

  • 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

    Example: nbinstallcmd -policy all_clients -schedule install812 -master_server primary1

    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 on the computer you want to upgrade. Refer to the nbinstallcmd command documentation for a list of all possible options and examples of command usage.

NetBackup Commands Reference Guide