Please enter search query.
Search <product_name> all support & community content...
Article: 100016039
Last Published: 2018-11-21
Ratings: 0 1
Product(s): Backup Exec
Problem
How to perform a quick test connection to the Backup Exec SQL instance.
Solution
The process described in this document will verify the existence of the Veritas Backup Exec (tm) SQL database and confirm that a connection can be made to it. If problems are encountered in this process, there may be a problem with the Backup Exec SQL instance or the Windows Database Components Open Database Connectivity (ODBC).
Go to the Backup Exec media server desktop and perform the following:
1. Right-click on the desktop and click New | Text Document (Figure1).
Go to the Backup Exec media server desktop and perform the following:
1. Right-click on the desktop and click New | Text Document (Figure1).
Figure1:
2. Give the file name a
.udl extension (Figure2).
Figure2:
2a. Note that if the option to "Hide extensions for known file types" is set, the operating system will not allow the extension to be renamed from .txt to .udl. In that case, create a folder on the desktop, go into the folder, and turn off the settting for "Hide extensions for known file types" in the Folder Options / View for this folder.
3. Right-click on the newly created file and select
Properties (Figure3).
Figure3:
4. Click on the Provider tab, select Microsoft OLE DB Provider for SQL Server, and then click Next (Figure4).
Figure4:
5. Click the Connection tab. In the Select or enter a server name field, type the server name of the Backup Exec media server, then type a backslash, and then type BKUPEXEC (or instance name if custom installation was performed). That is,
<server_name>\ INSTANCEname
(Figure5).
Figure 5:
a. In the
Enter information to log on to the server section, select
Use Windows NT Integrated Security (Figure5).
b. In the
Select the database on the server list, click
BEDB (Figure5).
c. Click
Test Connection (Figure 5), and verify that a successful response is received.
6. If there are connection errors, verify that the Backup Exec SQL instance service is running (Figure6).
Figure 6:
7. If the service is running, verify that the SQL database connectors are present by running the Microsoft Component Checker, available on the Microsoft Web site. This utility will display a list of missing files. For more infomarmation check https://support.microsoft.com/kb/301202.
8. Database components used for the Backup Exec SQL MSDE instance include DBNETLIB.DLL, SQLSRV32.DLL, SQLSRV32.RLL, among others. See the Microsoft Release Manifest for the Microsoft Data Access Components (MDAC) version installed to determine what file versions are appropriate.