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

Getting started with Data Collector clustering

  1. Install the Veritas NetBackup Data Collector on shared volume attached to the active node.

  2. On the same node, delete the start up scripts, by running the command:

     #  find /etc -name "*aptare*"
  3. Manually delete the following files:

    /etc/rc.d/rc0.d/K30aptare_agent
    /etc/rc.d/rc3.d/S80aptare_agent
    /etc/rc.d/rc3.d/K40aptare_agent
    /etc/rc.d/rc5.d/S80aptare_agent
    /etc/rc.d/rc5.d/K40aptare_agent
  4. Update the /etc/hosts file with IP and hostname mapping of aptareagent portal on all the cluster nodes.

  5. Using Veritas Infoscale Availability (VCS), create a separate service group for the agent. The following set of screen shots show the visual representation in VCS. There are multiple methods to set up the configuration. These instructions use the main.cf to setup.

    See Main.cf.

  6. Create a file /opt/aptare_scripts/aptare_dc_monitor.sh on all the cluster nodes with the following. Ensure execute permission is provided to the file for root user as owner.

    #!/bin/sh
    
    # APTARE_HOME should be set to the base path where aptare 
    # data-colletor is installed
    APTARE_HOME="/aptare_vol"
    
    # Exit codes that VCS understands
    E_APTARE_IS_ONLINE=110
    E_APTARE_IS_OFFLINE=100
    E_APTARE_IS_UNKNOWN=99
    
    SCRIPT="${APTARE_HOME}/mbs/bin/aptare_agent"
    
    if [ ! -f ${SCRIPT} ]; then
        exit $E_APTARE_IS_OFFLINE
    fi
    
    ${SCRIPT} status | grep 'WatchDog is running' >/dev/null 2>&1
    ret=$?
    if [ "$ret" -eq "0" ]; then
       exit $E_APTARE_IS_ONLINE
    else
       /usr/bin/ps -ef | grep -v grep |  grep -i aptare | 
       grep UpgradeManager  > /dev/null 2>&1
       upgrademanager_running=$?
       if [ "${upgrademanager_running}" -eq "0" ]; then
          exit $E_APTARE_IS_UNKNOWN
       fi
       exit $E_APTARE_IS_OFFLINE
    fi