Substituting ODBC for JDBC to Connect to SQL Server for Symantec Backup Exec Version 9.2.00

Substituting ODBC for JDBC to Connect to SQL Server for Symantec 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:

1. Obtain a copy the servers.csv file from the Portal Server (the one that you created to load the Backup Exec servers into the database).

2. Edit servers.csv and delete 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

3. Save the file to $APTARE_HOME/mbs/conf as odbcservers.conf on the Data Collector server.

5. Set up the ODBC DSN for each of the Backup Exec servers in odbcservers.conf, 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 odbcservers.conf.

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:

The DSN needs to be of the form hostname_BKUPEXEC, where hostname is the second token in odbcservers.conf.