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

NetBackup master server web server user and group creation

Beginning with NetBackup 8.0, the NetBackup master server includes a configured 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).

Note:

For security purposes, do not create web server users or groups with administrator or superuser privileges.

You can use numerous procedures to create users and groups in operating systems. Some specific approaches are shown, but other methods may accomplish the same goal. The home directory path, user name, and group names are not hard-coded, and can be changed. The default local user name is nbwebsvc, and the default local group name is nbwebgrp. The user and group must have sufficient permissions to run daemons.

More information about this topic is available.

See Upgrade requirements for UNIX and Linux.

Please be aware of the operating system-specific account and group requirements:

  • In UNIX and Linux clustered environments, make sure that the local accounts are defined consistently on all cluster nodes. The UID must be the same for each local account. You can use LDAP accounts on UNIX.

  • For Windows clustered master servers, you must use a domain account. You can use a domain account for non-clustered environments, but it is not required.

  • For Windows clustered master servers, you must use a domain group.

The NetBackup Master Server installation fails if any of these requirements are not met. On Windows, you are asked to provide the password for the user account as part of the installation process.

Note:

If the password associated with the web server account expires after initial configuration, NetBackup provides no notification the password has expired. This behavior is normal and expected, as the operating system manages the account and the password.

As long as the web server remains active, the account and the web server continue to operate normally.

When the web server is restarted, or if you attempt to restart the nbwmc service, the service fails to start, due to the expired password. Navigate to the appropriate area in the operating system, supply the correct password, and restart the service.

More information about the web services account and group is available. See the Veritas NetBackup Security and Encryption Guide and the section on the web services account.

To create the local user account and the local group:

  1. Create a local group.
    • Linux and UNIX: # groupadd nbwebgrp

    • Windows: C:\>net localgroup nbwebgrp /add

  2. Create a local user.
    • Linux and UNIX:# useradd -g nbwebgrp -c 'NetBackup Web Services account' -d /usr/openv/wmc nbwebsvc

    • Windows: C:\>net user nbwebsvc strong_password /add

  3. (Conditional) For Windows only, make the user a member of the group:

    C:\>net localgroup nbwebgrp nbwebsvc /add

  4. (Conditional) For Windows only, grant the Log on as a service right to the user:
    • Go to Control Panel > Administrative Tools > Local Security Policy.

    • Under Security Settings, click Local Policies > User Rights Assignment.

    • Right-click on Log on as a service and select Properties

    • Add the local user. The default local user name is nbwebsvc.

    • Save your changes and close the Properties dialog for Log on as a service.