Veritas NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup (8.1)
  1. Introduction
    1.  
      About the NetBackup 8.1 Upgrade Guide
    2. About changes in NetBackup 8.1
      1.  
        About MSDP changes
      2.  
        About certificate requirements for NetBackup 8.1
      3.  
        NetBackup Bare Metal Restore functionality not supported for restoring NetBackup 8.1 clients
      4.  
        SCCM and Chef deployment tools and documentation now available
    3.  
      Potential required changes for NetApp clusters
    4.  
      About automatic file changes from an upgrade
    5.  
      Errors when Bare Metal Restore information is replicated using Auto Image Replication
    6.  
      Known catalog backup limitation
    7.  
      About Veritas Services and Operations Readiness Tools
    8.  
      Recommended SORT procedures for new installations
    9.  
      Recommended SORT procedures for upgrades
    10.  
      About the NetBackup preinstall checker
  2. Planning for an upgrade
    1.  
      About planning a NetBackup 8.1 upgrade
    2.  
      How to plan for an upgrade to NetBackup 8.1
    3.  
      Creating the user account to support the NetBackup web server
    4.  
      Special guidelines for AIX master servers
    5.  
      MSDP changes in NetBackup 8.1
    6.  
      About security certificates for NetBackup hosts
  3. Master server upgrade
    1.  
      About master server upgrades
    2.  
      Preinstall procedure for upgrading to NetBackup 8.1
    3.  
      Performing local, remote, or clustered server upgrades on Windows systems
    4.  
      Performing silent upgrades on Windows systems
    5.  
      Upgrading UNIX/Linux server software to NetBackup 8.1
    6.  
      Post-install procedure for upgrading to NetBackup 8.1
    7. About mounting the NetBackup software media
      1.  
        Mounting NetBackup software media on UNIX or Linux systems
    8.  
      About NetBackup startup and shutdown scripts
    9.  
      Completing your system update after an upgrade
  4. Media server upgrade
    1.  
      Upgrading NetBackup media servers to NetBackup 8.1
  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. 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.  
      About the NetBackup answer file
    5.  
      Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1
    6.  
      About NetBackup software availability
    7.  
      About the NetBackup media kit
    8.  
      About the NetBackup Electronic Software Distribution (ESD) images
    9.  
      Additional post-upgrade steps for NetApp clusters
    10.  
      Using NetApp disk arrays with Replication Director
    11.  
      About compatibility between NetBackup versions
    12.  
      Installation and 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.  
      Upgrading clients after servers are upgraded
    16.  
      Install and upgrade of the UNIX and Linux client binaries with native installers
    17.  
      Removing a clustered media server by migrating all data to a new media server
    18.  
      Disabling the connection between your NetBackup OpsCenter server and your NetBackup Master Server
    19.  
      Post upgrade procedures for Amazon cloud storage servers

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

The source and the destination systems must run Windows 2008, 2008 R2, 2012, 2012 R2, or 2016 Server.

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)

  • Before you begin the install or the upgrade, take all NetBackup resources offline except for the shared disk resource, the virtual IP, and the virtual name.

  • Install or upgrade NetBackup from the active node (the node with the shared disk resource, virtual IP, and virtual name).

  • The computer or the 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.

  • You must take the VCS NetBackup resource offline before you begin the install or the upgrade.

    Note:

    Make sure that shared disk and IP resources are online during the install or the upgrade on active node.

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.