Veritas NetBackup™ Flex Scale Best Practices and Troubleshooting Guide

Last Published:
Product(s): Appliances (3.2)
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 port requirements
    4.  
      Considerations for using IPv6 addresses
    5.  
      Considerations for configuring disaster recovery
  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. Forwarding logs to an external server
      1.  
        Configuring log forwarding
      2.  
        Modifying log forwarding settings using the UI
      3.  
        Removing log forwarding
    6.  
      Error messages displayed during the pre-upgrade check
    7. 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 license error after successfully configuring the cluster
      8.  
        Resource monitoring and remediation

Resource monitoring and remediation

In NetBackup Flex Scale 3.2.100, if memory utilization reaches the threshold of 97%, the NetBackup Flex Scale node is brought down. You can confirm that the node is down in the following ways.

  • The ASC /log/autosupport/collector.log file has a INFO level log entry with a value greater than or equal to 97. Search for the value of the memory used_percentage parameter in the collector.log file.

  • A crash dump file gets created on the system default path.

  • The system logs have entry for node reboot.