NetBackup IT Analytics - How to troubleshoot most common Data collection issues

Description

The purpose of this article is to provide some pointers to address the most common reasons why NetBackup IT Analytics Data Collector may stop collecting data.

1. Verify that the Data Collector is online

• From the Portal webui browse to Admin > Data Collection >  Collector Administration
• If offline, log on to the Data Collector server and ensure the Data Collector service is running.
  • UNIX: /usr/openv/analyticscollector/mbs/bin/aptare_agent status
  • Windows: Use the Windows Services module to check the Aptare Agent status.

If stopped, manually start it:

• UNIX: /usr/openv/analyticscollector/mbs/bin/aptare_agent start
• Windows: Use the Windows Services module to start the Aptare Agent service

2. Verify that the Data Collector version (aptare.jar) matches (or is compatible) with the Upgrade Manager version.

• From the Portal webui browse to Admin > Data Collection >  Collector Administration
• From the Portal webui browse to Admin > Data Collection >  Collector Updates

3. Verify that the Data Collector policy is configured properly.

• From the Portal webui browse to Admin > Data Collection >  Collector Administration > Expand the Data Collector > edit the affected Data Collector policy.
  • Verify that the Backup software Location has the correct path. 
  • Verify that the User credentials are correct.
  • Verify that the Collection method is set properly.
• If the Data Collector software is installed on the NetBackup Primary server, there is no need to specify user credentials or API key.
• For some subsystems that require an API Key:
  • Ensure that the username and API key is configured within the Data Collector policy, especially if the collection method is via SSH or WMI.
  • The API key can also be configured within Portal webui > Inventory > Hosts > [select the host] > Actions > Edit...