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

CRON expressions and probe schedules

Many Data Collector policy configurations require a schedule. Native CRON expressions are supported for fine-tuning a schedule. The format for the schedule follows the CRON standard:

*

minutes

*

hours

*

day of month

*

month

*

day of week

Table: Probe Schedule Allowed Values

Field

Allowed Values

minutes

0-59 (0 is "on the hour")

hours

0-23

day of month

1-31

month

1-12

day of week

0-6 (0 is Sunday)

  • NetBackup IT Analytics supports a maximum of 80 characters in a CRON expression.

Special Characters:

  • A field may be an asterisk (*), which means the full range - i.e., "first" to "last". However, a * in the minutes position is not permitted, as this would excessively trigger the probe - every minute.

  • A forward slash (/) can be used to specify intervals.

  • Use a dash (-) to specify a range.

  • The CRON expression for the last day of the month, denoted by the letter L, is not supported.

Table: Probe Schedule fields example

Probe Schedule Examples

Scheduled Run Time

0 14-15 * * 1

On the hour, every Monday, between 2 and 3pm

Note:

A zero in the minutes position denotes the beginning of the hour.

30 9-13 * * 1-5

9:30, 10:30, 11:30, 12:30, and 13:30, Monday through Friday.

0 */2 * * *

To run the probe every 2 hours, put */2 in the hour position. This schedules the probe at 2am, 4am, 6am, 8am, 10am, 12pm, 2pm, and so on.

*/30 * * * *

Every 30 minutes

*/20 9-18 * * *

Every 20 minutes between 9 am and 6 pm

*/30 * * * 1-5

Every 30 minutes, Monday through Friday

1 2 * * *

2:01 every day

30 9,11 * * *

9:30 and 11:30 every day