MStevensAC Posted February 7, 2008 Report Share Posted February 7, 2008 My apologies up front to any who are tired of answering this question - but... Using 7.5 to back up the SQL server on my single SBS2003R2 server (with all appropriate licenses and permissions), the SQL container shows up only with Master, Model, and MSDB databases. The ones I care about don't show up on the list. I've tried many of the suggestions in other posts, but most of them seem to address the SQL container not showing up at all, which is not relevant in my case. I'm sure it's something I'm missing, and I'm sure somebody knows what it is... Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 7, 2008 Report Share Posted February 7, 2008 Can you be more specific about the permissions being used? What authentication method are you using? SQL or domain authentication? Quote Link to comment Share on other sites More sharing options...
MStevensAC Posted February 7, 2008 Author Report Share Posted February 7, 2008 As I gleaned from another post, the Retrospect Backup User has been included as a domain admin, a domain user, a backup admin, and a local admin (which did enable the Exchange backup, which was good), and the authentication is by domain (using the Retrospect Backup User). The system databases show up, but not any others. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 7, 2008 Report Share Posted February 7, 2008 I would try using SQL authentication to see if the results are different. Quote Link to comment Share on other sites More sharing options...
MStevensAC Posted February 8, 2008 Author Report Share Posted February 8, 2008 I couldn't get it to accept any SQL authorization - admin or sa. The missing databases are available to authorized users, and can be "backed up" from within the SQL manager. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 8, 2008 Report Share Posted February 8, 2008 If authentication is failing, then check the SQL Enterprise manager logs to see why the authentication is being rejected. You can also check the Windows Event Logs. Quote Link to comment Share on other sites More sharing options...
MStevensAC Posted February 8, 2008 Author Report Share Posted February 8, 2008 So... In the event log, corresponding to the Retrospect backup attempt, this error shows up: Event Type: Error Event Source: SQLVDI Event Category: None Event ID: 1 ... Computer: SBSRV01 Description: SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$SBSRV01. ErrorCode=(1060)The specified service does not exist as an installed service... ------------------------ And there is in fact no service MSSQL$SBSRV01 (where SBSRV01 is the server name). There are instead several MSSQL$[insert database name here] services. I can successfully back up any of the databases from within SQL Server Management. Is there a way to configure Retrospect to handle this? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 8, 2008 Report Share Posted February 8, 2008 Retrospect uses VDI to talk to SQL. I wonder if the VDI needs repair. I don't know if this is the same issue or not: http://support.microsoft.com/default.aspx?scid=KB%3Ben-us%3Bq280759 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 8, 2008 Report Share Posted February 8, 2008 Also see http://kb.dantz.com/article.asp?article=1114&p=2 Quote Link to comment Share on other sites More sharing options...
MStevensAC Posted February 25, 2008 Author Report Share Posted February 25, 2008 Still trying to figure this one out - and something occurred to me while staring at the screen for the umpteenth time: The missing databases are all separate SQL instances. So now the question becomes whether I can back up separate instances, or if not (which would be "bad") how can I specifiy which one is included (there is one of these missing db's that I am most concerned about - if I had to, the others could disappear without much heartache). Quote Link to comment Share on other sites More sharing options...
MStevensAC Posted April 7, 2008 Author Report Share Posted April 7, 2008 Don't interpret me as being pushy - or anxious... But... Retrospect (with the most recent updates) is still only picking up the system databases "master", "model", and "msdb". I ran through the steps above, with no change in behavior. If anybody has any ideas where to go next, let me know (and go ahead and assume I'm missing something obvious - since I probably am :-) Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 8, 2008 Report Share Posted April 8, 2008 Retrospect should be able to handle multiple instances of SQL, but I have seen issues when 2 different versions of SQL are installed. You can download and try the latest beta for Retrospect 7.5, which I think may contain at least 1 SQL bug fix. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.