Jump to content
vac

login to the SQL Server failed

Recommended Posts

Hello everybody,

 

I run a Microsoft SQL 2008 on a Windows 2008 Server system. Retrospect version 7.6.123 is installed on a seperate backup server. I installed the Retrospect client without any problems on the SQL Server. I can add the client within Retrospect but the login to the SQL-Server database failed. The SQL Server runs in mixed mode, but both methods (Domain login or SQL login) to access the server failed. As stated in the releases notes, the current version should support this constellation.

 

Any ideas?

 

best regards

Share this post


Link to post
Share on other sites

Did you create an RBU account for Retrospect? What groups is it a member of?

 

What exactly happens when you try to authenticate with Retrospect to the SQL server?

Share this post


Link to post
Share on other sites

Hello,

 

we set up a special "service-account" for backup this SQL-Server in the target domain. This account is member of the following groups:

Domain Administrator and Backup Operator

 

As I said, I can add the client to retrospect, the SQL Server and the local Volume C is correctly displayed. When I click on the SQL icon I have to enter login credentials and can choose between:

1. use current RBU Information

2. use SQL Authentication

3. Use Domain Authentication

 

Number 1 is no option because we use this backup server to backup several servers from different domains (datacenter backup). I have to use option 2. or 3.

I tried for 2. the login data for the "sa" user, but this does not work. For option 3 I tried the login data for the "service-account", but this also failed.

 

best regards

Edited by Guest

Share this post


Link to post
Share on other sites

installing the backward compaitibility solved the problem partially. I can now login with the sa user, login as Active Directory user still fails.

 

best regards

Share this post


Link to post
Share on other sites

not as far as I know. We only get it working with the "sa" user.

Anyway, I don't care, cause we're go to switiching our backup software soon. I mean, hey, no agent for Exchange 2010 while other vendors have it already and there's still no date for availability? Sorry, but this is unbeliveable.

 

best regards

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×