NetBackup IT Analytics Data Collector Notes and Troubleshooting

Last Published:
Product(s): NetBackup IT Analytics (11.0)
  1. Data Collector Troubleshooting
    1.  
      Verify the Data Collector configuration
    2.  
      Verify Connectivity
    3.  
      Configuring web proxy updates
    4.  
      Collecting missed events for Veritas Backup Exec
    5.  
      Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
    6.  
      Useful Data Collection scripts for capacity
    7.  
      Host resources troubleshooting
    8.  
      Host resources: Check the status of the WMI proxy server
    9.  
      Host resources: Post-Installation verification
    10. Host resources: Check host connectivity using standard SSH
      1.  
        Checking Paths for SSH
      2.  
        Environment setting for bash users
    11.  
      Host resources: Check host connectivity
    12.  
      Host resources: Check host connectivity using Host Resource Configuration file
    13. Host resources: Generating host resource configuration files
      1.  
        Sample lines in an input file
    14.  
      Host resources: Check the execution of a command on a remote server
    15.  
      Host resources Data Collection
    16.  
      Host resources: Collection in stand-alone mode
    17. Configuring parameters for SSH
      1.  
        Configure channelWaitTime
      2.  
        Configure singleChannelSession
      3.  
        Configure sudoWithPassword
    18.  
      Identifying Windows file system access errors (File Analytics)
    19.  
      Collect from remote shares (File Analytics)
    20.  
      Adding a certificate to the Java keystore
  2. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports
  3. CRON Expressions and Probe Schedules
    1.  
      CRON expressions and probe schedules
  4. Clustering Data Collectors with VCS and Veritas NetBackup (RHEL 7)
    1.  
      Clustering Data Collectors with VCS and Veritas NetBackup (RHEL 7)
    2.  
      Prerequisites
    3.  
      Getting started with Data Collector clustering
    4.  
      Main.cf
    5.  
      Upgrading a clustered Data Collector
  5. Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
    1.  
      Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
    2.  
      Prerequisites
    3.  
      Getting with Started with Data Collector Clustering
    4.  
      Main.cf
    5.  
      Upgrading a Clustered Data Collector
  6. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports
  7. 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

Recover inadvertently deleted aptare.ks file

When aptare.ks gets deleted, there are no ways to encrypt/decrypt the keys stored in aptare_message_relay_keystore.properties. This procedure provides the steps to recover an inadvertently deleted keystore (aptare.ks) file.

To recover a keystore file:

  1. Login to the data collector system and navigate to its installation path: /Aptare/mbs/conf.
  2. Identify these files inside /Aptare/mbs/conf:

    • aptare_message_relay_certificate.pem

    • aptare_message_relay_keystore.ks

    • aptare_message_relay_keystore.properties

  3. Stop the Aptare Agent service on the data collector system.

    On a Windows system, you can stop the service from the Services Console, whereas you can use ./aptareagent stop command on Unix.

  4. Delete these files from /Aptare/mbs/conf.

    • aptare_message_relay_certificate.pem

    • aptare_message_relay_keystore.ks

    • aptare_message_relay_keystore.properties

  5. Login to the NetBackup IT Analytics Portal to generate a new keystore file.

    Since the certificate was changed, the portal will display a notification which states:

    Data Collector SSL certificate has not been downloaded 
for collector(s): <data_collector_name>.
  6. Go to Admin > Data Collection > Collector Administration and click the collector name to view its policies.
  7. Double-click the collector to invoke the Edit Collector window.
  8. Copy the Passcode value and save it for later use.
  9. Click Generate Key and download the key file.
  10. Copy the key file to /Aptare/mbs/conf folder on the data collector system. Ensure the file name is same as that of the data collector on the portal.
  11. On the data collector system, open the collector.properties file from /Aptare/mbs/conf and replace the COLLECTOR_PASSWORD value with the Passcode value copied from the Edit Collector window.
  12. Save the collector.properties file and start the Aptare Agent service.

    After the service starts:

    • A new aptare.ks is generated inside /Aptare/mbs/conf which consumes the new key file.

    • . The aptare_message_relay_certificate.pem, aptare_message_relay_keystore.ks, and aptare_message_relay_keystore.properties files are generated later shortly.

    • Since the certificate was changed, the portal will display a notification which states:

      Data Collector SSL certificate has not been downloaded 
for collector(s): <data_collector_name>.
  13. On the NetBackup IT Analytics Portal, go to Admin > Data Collection > Collector Administration and click the collector name to view its policies.
  14. Double-click the policy name for which SSL certificate needs to be downloaded. The policy configuration window is displayed.
  15. Click Download SSL Certificate. The certificate is downloaded to your system.
  16. Copy the certificate to the data sender trust store.