NetBackup IT Analytics Data Collector Notes and Troubleshooting
- Data Collector Troubleshooting
- Verify the Data Collector configuration
- Verify Connectivity
- Configuring web proxy updates
- Collecting missed events for Veritas Backup Exec
- Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
- Useful Data Collection scripts for capacity
- Host resources troubleshooting
- Host resources: Check the status of the WMI proxy server
- Host resources: Post-Installation verification
- Host resources: Check host connectivity using standard SSH
- Host resources: Check host connectivity
- Host resources: Check host connectivity using Host Resource Configuration file
- Host resources: Generating host resource configuration files
- Host resources: Check the execution of a command on a remote server
- Host resources Data Collection
- Host resources: Collection in stand-alone mode
- Configuring parameters for SSH
- Identifying Windows file system access errors (File Analytics)
- Collect from remote shares (File Analytics)
- Adding a certificate to the Java keystore
- Firewall Configuration: Default Ports
- CRON Expressions and Probe Schedules
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL 7)
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Firewall Configuration: Default Ports
- Maintenance Scenarios for Message Relay Server Certificate Generation
Checking Paths for SSH
If you find messages in the metadata.log file that indicate that some of the commands are not found, then most likely the reason for it is the paths have not been set properly.
NetBackup IT Analytics uses a non-interactive login shell to execute ssh commands on devices.
Check the environment setting for the shell by running the command.
[user@host ~] ssh <user>@<host> "env"
Check the PATH shown in the output and make sure that it contains the path to all the commands required for NetBackup IT Analytics for the OS platform of the host.
Sample PATH for each of the host operating system platforms:
Linux: /bin:/sbin:/usr/bin:/usr/sbin
Solaris: /usr/xpg4/bin:/usr/sbin:/usr/bin
AIX: /usr/bin:/usr/sbin
HPUX: /usr/bin:/usr/sbin:/opt/fcms/bin:/sbin
Note:
Since Veritas Volume Manager is supported, its path needs to be included in the PATH env variable.
In environments, make sure that the sudo path is also in the PATH shown in the output of the above command.