Veritas NetBackup™ Flex Scale Best Practices and Troubleshooting Guide

Last Published:
Product(s): Appliances (3.1)
Platform: NetBackup Flex Scale OS
  1. Introduction
    1.  
      Scope and intended audience
    2.  
      About NetBackup Flex Scale
    3.  
      About NetBackup Flex Scale nodes
  2. Configuration requirements
    1.  
      Physical environment
    2.  
      NetBackup Flex Scale configuration requirements
    3.  
      Firewall and network ports requirements
    4.  
      Considerations for using IPv6 addresses
  3. Best practices
    1.  
      Management network connectivity
    2.  
      Private network connectivity
    3.  
      Configuring AutoSupport for the appliance
    4.  
      Necessary software
  4. NetBackup Flex Scale tuning and sizing
    1.  
      Assigning media servers to a storage server
    2.  
      NetBackup Flex Scale tuning
  5. Troubleshooting NetBackup Flex Scale
    1.  
      NetBackup Flex Scale logs
    2.  
      Services management
    3.  
      Audit logs
    4. Collecting logs for cluster nodes
      1.  
        Uploading logs to Veritas Support
      2.  
        Downloading logs
    5.  
      Error messages displayed during the pre-upgrade check
    6. Troubleshooting NetBackup Flex Scale issues
      1.  
        If cluster configuration fails (for example because an IP address that was already in use is specified) and you try to reconfigure the cluster, the UI displays an error but the configuration process continues to run
      2.  
        Validation error while adding VMware credentials to NetBackup
      3.  
        NetBackup Web UI incorrectly displays some NetBackup Flex Scale processes as failed
      4.  
        Unable to create BMR Shared Resource Tree (SRT) on NetBackup Flex Scale Appliance
      5.  
        NetBackup configuration files are not persistent across operations that require restarting the system
      6.  
        Connection timeout errors during patch installs, upgrades, and rollback operations
      7.  
        Initial configuration wizard displays a driver node not selected error
      8.  
        Initial configuration wizard displays a license error after successfully configuring the cluster

NetBackup configuration files are not persistent across operations that require restarting the system

The VmTools.cfg and vixDiskLib.ini files do not persist after a node is restarted as a part of an operation such as upgrading or replacing a node.

Workaround:

Use the cp-nbu-config command to copy the NetBackup configuration files from the user's home space to the specified NetBackup configuration destination directory. A NetBackup administrator can use the cp-nbu-config command to create and edit a NetBackup touch configuration file in any of the following directories:

  • /usr/openv/netbackup

  • /usr/openv/netbackup/bin

  • /usr/openv/java

  • /usr/openv/lib/ost-plugins

  • /usr/openv/netbackup/bin/snapcfg

  • /usr/openv/netbackup/db/cloudSnap/credential

  • /usr/openv/netbackup/db/cloudSnap/proxy

  • /usr/openv/netbackup/db/config

  • /usr/openv/netbackup/db/event

  • /usr/openv/netbackup/db/images

  • /usr/openv/netbackup/db/media

  • /usr/openv/netbackup/ext/db_ext

  • /usr/openv/netbackup/ext/db_ext/db2

  • /usr/openv/var

  • /usr/openv/volmgr

  • /usr/openv/volmgr/database

To create or edit a touch configuration file

  1. Log in to the node.
  2. Create a new configuration file in the NetBackup administrator home directory, or use the cp command to copy an existing configuration file from its original location to the home directory. For example:

    cp /usr/openv/lib/ost-plugins/pd.conf ~/

  3. Make changes to the file in the home directory.
  4. Run the following command to install the file in its original directory or a supported destination directory:

    sudo /opt/veritas/vxapp-manage/cp-nbu-config configuration-file destination

    where configuration-file is the file that you created or edited, and destination is the directory where it needs to be installed.

    sudo /opt/veritas/vxapp-manage/cp-nbu-config ~/pd.conf /usr/openv/lib/ost-plugins