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

Audit logs

You can use the Settings > Audit logs tab to view the list of operations or events that are performed from the GUI or cluster-level CLI. All the operations and events which are triggered are logged on an audit log file as a single entry.

The following information is displayed for each operation or event:

  • Event: This specifies the name of the operation or event.

  • Date and time: This specifies the date and time when the operation or event was completed.

  • User: This specifies the user who initiated the operation or event.

  • Severity: This specifies the severity of the logged message for the operation or event.

  • Description: This gives information about the operation or event.

You can also search for events by using the search box that is present above the audit log entry table. The search can be done based on event name, username, severity, description or sub-string of description.

The audit logs can be collected as part of Infrastructure module from the Basic tab of Generate Log Package. After you extract the collected log package, the audit logs are present in the infrastructure/auditlog directory. The audit logs can also be collected from the Advanced tab of Generate Log Package. You can collect the audit log file from /vx/MASTER_LOG_FS/auditlog/auditlog.log location in the Advanced tab.

The audit log captures the operation or event that a user has initiated. If that operation involves execution of some suboperations, then those suboperations also get logged as a new audit log entry.