Veritas NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup (9.0)
  1. Introduction
    1.  
      About the NetBackup 9.0 Upgrade Guide
    2.  
      Available NetBackup upgrade methods
    3. About changes in NetBackup 9.0
      1.  
        Java GUI and JRE installation optional for some computers
      2.  
        Logging directory permissions require reset on rollback
      3.  
        Upgrades from NetBackup 7.6.0.4 and earlier are not supported
      4.  
        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 9.0 upgrade
      2.  
        How to plan for an upgrade to NetBackup 9.0
      3.  
        Known catalog backup limitation
      4.  
        About security certificates for NetBackup hosts
      5.  
        About automatic file changes from an upgrade
    2. About upgrade tools
      1.  
        About Veritas Services and Operations Readiness Tools
      2.  
        Recommended SORT procedures for upgrades
      3.  
        Recommended SORT procedures for new installations
      4.  
        About the NetBackup preinstall checker
    3. Upgrade operational notes and limitations
      1.  
        Creating the user account to support the NetBackup web server
      2.  
        About NetBackup 9.0 support for Fibre Transport Media Server with RHEL 7.5
      3.  
        MSDP changes in NetBackup 8.1
      4.  
        Potential required changes for NetApp clusters
      5.  
        Errors when Bare Metal Restore information is replicated using Auto Image Replication
      6.  
        Upgrade issue with pre-8.1 clients and 8.1 or later media servers
  3. Master server upgrade
    1.  
      About master server upgrades
    2.  
      Preinstall procedure for upgrading to NetBackup 9.0
    3.  
      Performing local, remote, or clustered server upgrades on Windows systems
    4.  
      Performing silent upgrades on Windows systems
    5.  
      Upgrading UNIX and Linux server software to NetBackup 9.0
    6.  
      Post-install procedure for upgrading to NetBackup 9.0
    7.  
      About NetBackup startup and shutdown scripts
    8.  
      Completing your system update after an upgrade
  4. Media server upgrade
    1.  
      Upgrading NetBackup media servers to NetBackup 9.0
    2.  
      Silently upgrading NetBackup media server software on UNIX and 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.  
      Upgrading UNIX and Linux clients with the NetBackup upgrade script
    3.  
      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 master 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 master server web server user and group creation
    2.  
      Generate a certificate on the inactive nodes of a clustered master 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.  
      Persistent Java Virtual Machine options
    8.  
      About RBAC bootstrapping
    9.  
      About NetBackup software availability
    10.  
      Additional post-upgrade steps for NetApp clusters
    11.  
      Using NetApp disk arrays with Replication Director
    12.  
      About compatibility between NetBackup versions
    13.  
      Upgrade requirements for UNIX and Linux
    14.  
      Installation and upgrade requirements for Windows and Windows clusters
    15.  
      Requirements for Windows cluster installations and upgrades
    16.  
      Removing a clustered media server by migrating all data to a new media server
    17.  
      Disabling the connection between your OpsCenter server and your NetBackup Master Server
    18.  
      Post upgrade procedures for Amazon cloud storage servers
    19.  
      Upgrading clients after servers are upgraded
  9.  
    Index

Upgrade requirements for UNIX and Linux

Table: NetBackup requirements for UNIX and Linux describes the requirements to prepare your UNIX and Linux systems for NetBackup upgrade. 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.

Table: NetBackup requirements for UNIX and Linux

Check

Requirement

Details

 

Operating System

Memory

  • Master servers in a production environment with several database agents enabled should have a minimum of 16 GB of memory and four cores each.

    NetBackup does not enforce minimum memory requirements. Veritas does, however, recommend using at least the minimum recommended memory. Failure to use the minimum recommended memory amounts can result in unacceptable performance.

  • Media servers in a production environment with several database agents enabled should have a minimum of 4 GB of memory each.

 

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 9.0

  • 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 master server is placed in a production environment.

General requirements

  • Ensure that the gzip and the gunzip commands are installed on the local system. 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 9.0.

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

  • Ensure that each node in the NetBackup cluster can run the ssh command or its 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.

More information about cluster requirements is available.

NetBackup Clustered Master Server Administrator's Guide

 

NFS compatibility

Veritas does not support installation of NetBackup in an NFS-mounted directory. File locking in NFS-mounted file systems can be unreliable.

 

Kernel reconfiguration

For some peripherals and platforms, kernel reconfiguration is required.

For more details, see the NetBackup Device Configuration Guide.

 

Linux

Before NetBackup installation, confirm the system libraries that are shown are present. If any library is not present, install the one provided by your operating system.

  • libnsl.so.1

  • insserv-compat

  • libXtst

 

Red Hat Linux

For Red Hat Linux, NetBackup requires server networking.

 

Other backup software

Veritas recommends that you remove any other vendor backup software currently 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 master 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 master server (or each node of a clustered master server). You must create these required account elements before installation. More information is available:

See NetBackup master server web server user and group creation.

Note:

Veritas recommends that you save the details of the user account that you use for the NetBackup Web Services. A master 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.

  1. Log in to the server as root.

  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

  5. Save and close the file.

 

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.

Note:

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