01-08-2014 04:25 AM
I am trying to configure MS SQl Db backup.
The server is added to client list.
Now when I go to DP>Backup>Backup specifications>MSSQL Server and configure the backup.
I give the client name and when I try to give application database name/instance name the DP would hung and it will not automatically popup with the appplication database name like it should be.
So i am not sure if I have missed something. Please help !
01-08-2014 07:02 AM
I have seen a problem occur when trying to configure Exchange backups mostly, a few with SQL, although in those cases, the problem was when the server was chosen, an Application Data base was not shown
On the SQL server, find the path to the SQL executables folder. Then, at the MS-DOS prompt on the SQL server, type the command:
to see if the path to the SQL executables is included. If not, add the path to the Windows environment variables on the SQL server
You didn't specify what version of Data Protector you are using, so I can't give you a page reference in the Integration Guide, but, here is what is says about this issue with Exchange
Add the 'Exchange_home\bin' directory to the Windows Path environment variable:
1. In the Windows Explorer, right-click
My Computer and click Properties.
2. In the Properties dialog box, click Advanced and then Environment Variables.
Path in the System Variables list and click Edit.
in the Variable Value text box and click OK.
If the integration is cluster-aware, perform this procedure on all cluster nodes.
So, instead of Exchange_home, make is SQL_Home
01-09-2014 12:30 PM
"In third step you have mentioend select Path. you mean Omniback/bin Path ? or some other?"
The path is that of the SQL_Home\bin directory
"Is there any license issue ?"
You will need an on-line extension license for windows (B6965), but, that is not affecting the problem that you are having
01-12-2014 11:14 PM
I tried what you suggested. Se the environmental variables.
But still when I try to select application database while configuring the SQL online backup, it woud hang and I could only see hour glass !! :(
01-22-2014 08:00 PM
I had a similar error with version 7.0, I did was put in the host file in the cell manager the name sql server complete with domain name and server sql host file the cell manager name complete with domain and integration of sql was made in good form
03-11-2014 07:23 AM
Essentially, all Application backups, such as SQL have their own Backup method. The 'sql_bar' is the way that DP connects to these methods and provides the media management and reporting for the backup. In the Integration Guide
Data Protector integrates with SQL Server through the Data Protector sql_bar.exe executable,
installed on SQL Server. It implements multiple virtual devices for backup and restore and transforms
SQL Server Virtual Device Interface (VDI) commands from SQL Server into Data Protector backup
or restore streams.
The VDI architecture allows the Data Protector General Media Agent to access data directly in the
SQL Server memory, provided the devices are directly attached to SQL Server. Therefore, high
backup and restore speed is achieved.
When you go into the Users context in the GUI, and right-click on any server, pick 'Add Component', and choose MS_SQL, DP will install any necessary files on that server, including 'sql_bar'
An SQL Server instance is configured during the creation of the first backup specification. The
configuration consists of setting the user account that Data Protector should use to connect to the
SQL Server instance. The specified login information is saved to the Data Protector SQL Server
instance configuration file on the Cell Manager.
This is done either using the GUI, or from the MS-DOS prompt on the SQL server
sql_bar config [-appsrv:SQLServerClient] [-instance:InstanceName]
The client system on which the SQL Server instance is running. This option is not required if
you run the command locally
The SQL Server instance name. If you omit this option, the default SQL Server instance is
The SQL Server user account (SQL Server authentication)
WindowsUser -password:password -domain:domain
The Windows domain user account (Windows authentication)
All of this is in the Microsoft Products integration guide