NetBackup IT Analytics Data Collector Notes and Troubleshooting
- Data Collector Troubleshooting
- Resolving Data Collectors connections issues - Linux specific
- Resolving Data Collectors connections issues - Windows specific
- Portal upgrade performance issues
- 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
- Override default Java Heap memory (XMX) value for Data Collector utilities
- Firewall Configuration: Default Ports
- CRON Expressions for Policy and Report Schedules
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Install and configure NetBackup IT Analytics Data Collector on MSCS environment
- Firewall Configuration: Default Ports
- Maintenance Scenarios for Message Relay Server Certificate Generation
Host resources: Check host connectivity
This utility displays information on the connection status of a list of host names, IP addresses, or a range of IP addresses.
chkHostConnection.{sh|bat} HostAddresses userId password
[domain <domain>]
[exclude <excludeHostAddresses>] [wmiserver <wmiserver>]
[cto <connectTimeout>] [sto socketTimeout>]
[accessCmd=accessControlCommand>]Table: Hosts resources and their values.
Host Addresses | The hosts to verify. It can be hostname, IP address, or range of IP addresses, or a comma-separated list of them. |
|---|---|
domain | The Domain for the Windows hosts |
excludeHostAddresses | The hosts to be excluded from the HostAddresses list. It can be hostname, IP address, or range of IP addresses, or a comma separated list of them. |
wmiserver | Name of the WMI Proxy Server |
cto | Connection time-out in milliseconds |
sto | Socket time-out in milliseconds |
accessCmd | An access control command such as |
As a result: for each host, the status of the connection is listed.
Connectivity Check Server List: [172.16.1.10, 172.16.1.12, APTAREaix1] 172.16.1.10 ............. SUCCESS 172.16.1.12 ............. SUCCESS
chkHostConnection.{sh|bat} HostAddresses userId password [domain <domain>] [exclude <excludeHostAddresses>] [wmiserver <wmiserver>] [cto <connectTimeout>] [sto socketTimeout>] [accessCmd=accessControlCommand>]HostAddresses | The hosts to verify. It can be hostname, IP address, or range of IP addresses, or a comma-separated list of them. |
domain | The Domain for the Windows hosts |
excludeHostAddresses | The hosts to be excluded from the HostAddresses list. It can be hostname, IP address, or range of IP addresses, or a comma separated list of them. |
wmiserver | Name of the WMI Proxy Server |
cto | Connection time-out in milliseconds |
sto | Socket time-out in milliseconds |
accessCmd | An access control command such as |
For each host, the status of the connection is listed.
Connectivity Check Server List: [172.16.1.10, 172.16.1.12, APTAREaix1] 172.16.1.10 ............. SUCCESS 172.16.1.12 ............. SUCCESS