Re: MSSQL DB backup integration (1220 Views)
Reply
Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 1 of 18 (1,345 Views)

MSSQL DB backup integration

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 !

HP Expert
Posts: 1,704
Registered: ‎08-14-2013
Message 2 of 18 (1,322 Views)

Re: MSSQL DB backup integration

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:

 

          path

 

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.

3. Select

            Path in the System Variables list and click Edit.

4. Add

           Exchange_home\bin

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

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 3 of 18 (1,314 Views)

Re: MSSQL DB backup integration

Thanks for your reply.

In third step you have mentioend select Path. you mean Omniback/bin Path ? or some other?

 

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 4 of 18 (1,306 Views)

Re: MSSQL DB backup integration

Is there any license issue ?

HP Expert
Posts: 1,704
Registered: ‎08-14-2013
Message 5 of 18 (1,300 Views)

Re: MSSQL DB backup integration

"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

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 6 of 18 (1,258 Views)

Re: MSSQL DB backup integration

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 !! :(

HP Expert
Posts: 1,704
Registered: ‎08-14-2013
Message 7 of 18 (1,245 Views)

Re: MSSQL DB backup integration

Open a case with the response center

Honored Contributor
Posts: 541
Registered: ‎11-25-2008
Message 8 of 18 (1,238 Views)

Re: MSSQL DB backup integration

Hello

 

Please check that DP inet service into SQL server is running under SQL administrator account.

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 9 of 18 (1,224 Views)

Re: MSSQL DB backup integration

I chnaged SQL Inet service to run under SQL Admin login but still no luck.

I still cant configure the backup ! :(

Highlighted
HP Expert
Posts: 1,704
Registered: ‎08-14-2013
Message 10 of 18 (1,220 Views)

Re: MSSQL DB backup integration

I have probably gone as far as I can with this, time to open a case with the response center, and have Engineering look at this

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 11 of 18 (1,210 Views)

Re: MSSQL DB backup integration

I have raised a support case with HP team but still no luck ! not sure how long it can take !

Occasional Contributor
Posts: 5
Registered: ‎07-06-2011
Message 12 of 18 (1,199 Views)

Re: MSSQL DB backup integration

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

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 13 of 18 (1,191 Views)

Re: MSSQL DB backup integration

I have made host entry on both the nodes but no help !

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 14 of 18 (1,147 Views)

Re: MSSQL DB backup integration

what is sql_bar.exe and how to install and where to install.Also want to know what to be configured from sql server end

HP Expert
Posts: 1,704
Registered: ‎08-14-2013
Message 15 of 18 (1,142 Views)

Re: MSSQL DB backup integration

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'

 

Then,

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]

[-dbuser:SQLServerUser -password:password]

 

-appsrv:

SQLServerClient

The client system on which the SQL Server instance is running. This option is not required if

you run the command locally

-instance:

InstanceName

The SQL Server instance name. If you omit this option, the default SQL Server instance is

configured

-dbuser:

SQLServerUser -password:password

The SQL Server user account (SQL Server authentication)

-dbuser:

WindowsUser -password:password -domain:domain

The Windows domain user account (Windows authentication)

 

All of this is in the Microsoft Products integration guide

 

Regular Advisor
Posts: 124
Registered: ‎07-17-2013
Message 16 of 18 (1,117 Views)

Re: MSSQL DB backup integration

It is still isnt working. I am not sure why it cant tkae the instance name. verytiem I try to configure it screen would hang.

any license constraint ?

Occasional Visitor
Posts: 4
Registered: ‎02-10-2011
Message 17 of 18 (341 Views)

Re: MSSQL DB backup integration

Hi,

 

Have you got your MSSQL backup configuration setup already?

 

If not, then you can try these steps:

1. Uninstal DP software on your MSSQL machine

2. Export the MSSQL machine from the DP client list

3. Add the MSSQL machine to the DP client list and install the components needed especially the MSSQL Integration component

4. Try configuring MSSQL backup for your MSSQL machine

 

-louie

Honored Contributor
Posts: 729
Registered: ‎01-16-2014
Message 18 of 18 (329 Views)

Re: MSSQL DB backup integration

On your SQL-Client run "sql_bar.exe list_inst", does that list the Instances?

If not you have an configuration issue in the MSSQL-Server.

 

Make sure you have NameResolution working properly on both the SQL-Client and the CellServer (including ReverseLookup)

Also make sure both Systems can connect to each other via Port 5555 properly.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.