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

Resolving Data Collectors connections issues - Linux specific

Perform the following steps to resolves the data connections issues:

  1. Verify that the tomcat-agent and apache services are running on the portal.

  2. Verify that the key file is generated when the data collector was created.

  3. On the portal, perform wget to the URL of the data receiver. The expected response is: Index.html file.

    Note:

    This step bypasses the network and validates that the data receiver is up and running.

  4. On the data collector, verify that the data receiver URL resolves via NSLOOKUP. If not then specify the data receiver IP address and name to the data collector's host file.

    Verify using wget from the data collector that a response back, index.html page, is received. If not then ,verify if the firewall is blocking the access to port 80/443, depending upon configurations.

  5. Execute the command ../mbs/bin/updateconfig. The expected response is: quick return to the command prompt. If not then: verify that the /opt/aptare/datarcvrconf/collectorConfig.global.properties on the portal has the correct URL.

  6. Execute the checkinstall. If there is initial communication but errors, confirm the data collector name, passcode, and URL are correct.

  7. Examine the <Data Collector home>/mbs/conf/collector.properties file and verify that the collector name, collector password, and URL were specified appropriately during the installation.

  8. Verify that the collector service is started, and Watchdog is running.

  9. Ensure the understanding that if the portal is running a later upgrade than the GA data collector that upgrade will initiate right after DC connects, and the data collector will go offline for a period during the upgrade.