NetBackup IT Analytics Data Collector Notes and Troubleshooting

Last Published:
Product(s): NetBackup IT Analytics (11.6)
  1. Data Collector Troubleshooting
    1.  
      Resolving Data Collectors connections issues - Linux specific
    2.  
      Resolving Data Collectors connections issues - Windows specific
    3.  
      Portal upgrade performance issues
    4.  
      Verify the Data Collector configuration
    5.  
      Verify Connectivity
    6.  
      Configuring web proxy updates
    7.  
      Collecting missed events for Veritas Backup Exec
    8.  
      Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
    9.  
      Useful Data Collection scripts for capacity
    10.  
      Host resources troubleshooting
    11.  
      Host resources: Check the status of the WMI proxy server
    12.  
      Host resources: Post-Installation verification
    13. Host resources: Check host connectivity using standard SSH
      1.  
        Checking Paths for SSH
      2.  
        Environment setting for bash users
    14.  
      Host resources: Check host connectivity
    15.  
      Host resources: Check host connectivity using Host Resource Configuration file
    16. Host resources: Generating host resource configuration files
      1.  
        Sample lines in an input file
    17.  
      Host resources: Check the execution of a command on a remote server
    18.  
      Host resources Data Collection
    19.  
      Host resources: Collection in stand-alone mode
    20. Configuring parameters for SSH
      1.  
        Configure channelWaitTime
      2.  
        Configure singleChannelSession
      3.  
        Configure sudoWithPassword
    21.  
      Identifying Windows file system access errors (File Analytics)
    22.  
      Collect from remote shares (File Analytics)
    23.  
      Adding a certificate to the Java keystore
    24.  
      Override default Java Heap memory (XMX) value for Data Collector utilities
  2. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports
  3. CRON Expressions for Policy and Report Schedules
    1.  
      CRON expressions for policy probe schedules
    2.  
      CRON expressions for scheduling reports
  4. Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
    1.  
      Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
    2.  
      Prerequisites
    3.  
      Getting started with Data Collector clustering
    4.  
      Configuring the Data Collector
    5.  
      Upgrading a clustered Data Collector
    6.  
      Considerations when Data Collector is pointing to Alta Domain Management
  5. Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
    1.  
      Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
    2.  
      Prerequisites
    3.  
      Getting Started with Data Collector Clustering
    4.  
      Main.cf
    5.  
      Upgrading a Clustered Data Collector
    6.  
      Manage cluster configuration during NetBackup upgrade (Windows)
  6. Install and configure NetBackup IT Analytics Data Collector on MSCS environment
    1.  
      Cluster Data Collectors with MSCS on Windows
    2.  
      Perform cluster configurations
    3.  
      Upgrade NetBackup IT Analytics Data Collector in MSCS
    4.  
      Uninstall NetBackup IT Analytics Data Collector
    5.  
      Steps to perform before and after NetBackup upgrade
  7. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports
  8. Maintenance Scenarios for Message Relay Server Certificate Generation
    1.  
      Regenerate authentication certificate nearing expiry (or already expired)
    2.  
      Recover inadvertently deleted aptare.ks file
    3.  
      Authenticate new database with existing SSL certificates
    4.  
      SSL certificate authentication for a new data collector

Host resources troubleshooting

Use the following sequence of steps to determine the source of host resources data collection issues. All commands--except for the SSH commands and the WMI Proxy command--report errors to metadata.log. After executing a command, check the metadata.log file for error messages. If there is an error noted, correct the problem and then re-issue the command. If the command succeeds, proceed to the next command in this sequence:

  1. See Host resources: Check the status of the WMI proxy server.

  2. See Host resources: Post-Installation verification.

  3. See Host resources: Check host connectivity using standard SSH.

  4. See Host resources: Check host connectivity.

  5. See Host resources: Check the execution of a command on a remote server.

  6. See Host resources: Collection in stand-alone mode.