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

Management network connectivity

The eth1 port of the node is connected to the management network. Use the ping command to verify if the management network is available and the nodes are reachable:

ping -I eth1-interface-ip destination-ip

eth1-interface-ip is the IP address assigned to the eth1 interface.

destination-ip is the destination IP address.

For example:

mgmtip22.nbfs.com:~ # ping -I 192.168.70.22 192.168.70.10
PING 192.168.70.10 (192.168.70.10) from 192.168.70.22 : 56(84) bytes of data.
64 bytes from 192.168.70.10: icmp_seq=1 ttl=64 time=0.267 ms

--- 192.168.70.10 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.267/0.267/0.267/0.000 ms
mgmtip22.nbfs.com:~ #

If the customer's site does not allow the usage of ping command, use the arping command instead:

arping -I eth1 ipaddress

Verify the entries in the routing table for all the nodes:

network route show nodename=nodename