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

Services management

You can use the Settings > Services management tab to manage your storage services.

When there is a device failure or a new device is added, the device information may not be consistent. In such a scenario, you can Run full discovery to update the database with latest system settings and usage data.

You can fix service-related faults in the nodes of the cluster that are in running state. If a service has faulted because of issues in services such as the volume manager, NLM, deduplication, or the management console, you can Run auto fix and bring the service online after the issue has been resolved. No other operation should be initiated when you run AutoFix.

You can also call the POST/api/appliance/v1.0/management/autofix RESTful API to run auto fix.