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
Host resources: Check host connectivity using standard SSH
NetBackup IT Analytics uses SSH to communicate with devices to run SSH commands. Sometimes, a connectivity issue is simply an incorrect path to a host.
Note:
Use the following SSH commands before attempting to collect data.
To check host connectivity using standard SSH:
Check that the connection to a Host is successful, using the credentials provided.
[user@host ~] ssh <user>@<host> ls
Similarly, if you are using Telnet, check your host access via Telnet and run commands, as shown in the following step.
In access-controlled environments such as , a sudo user must be set up. Ensure that the sudo user can run the commands required for the host operating system platform.
To verify access:
[user@host ~] ssh <sudouser>@<host> "sudo <command>"
If this command results in errors, such as command not found, set up the paths correctly and re-run this command.
on page 11.
Paths should be set correctly for the commands to run.