Veritas NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup (8.3.0.2, 8.3.0.1, 8.3)
  1. Introduction
    1.  
      About the NetBackup 8.3 Upgrade Guide
    2.  
      Available NetBackup upgrade methods
    3. About changes in NetBackup 8.3
      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 Smart Meter
    5.  
      Best practices for Veritas Smart Meter
  2. Planning for an upgrade
    1. General upgrade planning information
      1.  
        About planning a NetBackup 8.3 upgrade
      2.  
        How to plan for an upgrade to NetBackup 8.3
      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 8.3 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 8.3
    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 8.3
    6.  
      Post-install procedure for upgrading to NetBackup 8.3
    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 8.3
    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.  
      About RBAC bootstrapping
    8.  
      About NetBackup software availability
    9.  
      Additional post-upgrade steps for NetApp clusters
    10.  
      Using NetApp disk arrays with Replication Director
    11.  
      About compatibility between NetBackup versions
    12.  
      Upgrade requirements for UNIX and Linux
    13.  
      Installation and upgrade requirements for Windows and Windows clusters
    14.  
      Requirements for Windows cluster installations and upgrades
    15.  
      Removing a clustered media server by migrating all data to a new media server
    16.  
      Disabling the connection between your OpsCenter server and your NetBackup Master Server
    17.  
      Post upgrade procedures for Amazon cloud storage servers
    18.  
      Upgrading clients after servers are upgraded
  9.  
    Index

Requirements for Windows cluster installations and upgrades

In addition to the normal server requirements, NetBackup cluster installations require special considerations.

The following describes the guidelines for NetBackup cluster installations and upgrades on Windows systems:

Table: Windows cluster requirements for installation and upgrade

Item

Requirement

Server operating system

 

Privileges

To perform clustered installations, you must have administrator privileges on all of the remote nodes in the cluster. Veritas recommends that you keep a record of all nodes in the cluster and what software exists on each node.

NetBackup virtual name and IP address

Have the virtual name and IP address for NetBackup 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 media servers

Clustered media servers are not supported.

Windows Server Failover Clusters (WSFC)

 

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.