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
Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
The Backup Exec data collector, by default, uses JDBC (Java Database Connectivity) to connect to the SQL Server database. In most cases, this is the preferred mechanism for communicating with the SQL Server. However, in some instances--for example, TCP/IP is disabled for the SQL Server--JDBC will not be feasible.
In these rare situations, you can configure ODBC (Open Database Connectivity) to connect. The main limitation of this option is that it requires that a DSN (Data Source Name) be set up for each Backup Exec server for which the data collector needs access.
Note:
The data collector can be configured to use a mixture of JDBC and ODBC for specific servers.
Use the following steps to turn on ODBC for specific servers:
Obtain a copy the file from the Portal Server (the one that you created to load the Backup Exec servers into the database).
Edit anddelete those servers that you do not want to use ODBC. The format of the entry in the CSV file is:
<windows_domain>, <host or ipaddress>, <ipaddress>, , , BKUPEXEC
Save the file to as on the Data Collector server.
Launch the ODBC Data Source Administrator window:
Control Panel > Administrative Tools > Data Sources (ODBC)
Set up the ODBC DSN for each of the Backup Exec servers in , as depicted in the following sequence of windows.
The DSN needs to be of the form hostname_BKUPEXEC, where hostname is the second token in .
Note:
If the hostname_BKUPEXEC form does not work (see the third window in the following example), try substituting the IP address for the hostname. If you use the IP address, be sure to make appropriate changes to the CSV file to comply with the following required format:
<windows_domain>, <ipaddress>, <ipaddress>, , , BKUPEXEC
The DSN needs to be of the form hostname_BKUPEXEC, where hostname is the second token in .
Note:
If the hostname_BKUPEXEC form does not work (see the third window in the following example), try substituting the IP address for the hostname. If you use the IP address, be sure to make appropriate changes to the CSV file to comply with the following required format:
<windows_domain>, <ipaddress>, <ipaddress>, , , BKUPEXEC
