Comprehensive data protection for all workloads
Post Reply
degauser
Novice
Posts: 6
Liked: never
Joined: Jan 09, 2020 5:55 am
Full Name: Sam Sepiol
Contact:

SQL Server Staging Translate Error

Post by degauser » Jan 09, 2020 1:49 pm

Hi all.

I've successfully upgraded from 2012 Express to 2016 Standart. Therefore I'd expect to do SQL Server Staging successfully. But I've encountered another error.

Image

As you can see above, the error message says "Some or all identity references could not be translated" and I get nothing to restore.

Dima P.
Product Manager
Posts: 11205
Liked: 948 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: SQL Server Staging Translate Error

Post by Dima P. » Jan 09, 2020 11:09 pm

Hello Sam,

Can you please clarify how authentication is configured for your staging server? You can use this article Configuring Staging SQL Server as a check list to make sure that all the required settings were set correctly. Cheers!

degauser
Novice
Posts: 6
Liked: never
Joined: Jan 09, 2020 5:55 am
Full Name: Sam Sepiol
Contact:

Re: SQL Server Staging Translate Error

Post by degauser » Jan 10, 2020 6:27 am

Immm. I'm not a database guy so I'll try to clarify as much as I can.

Let's name our servers. MSSQL Server is DBSRV and Veeam Server is VSRV (just to prevent conflictions.)

The process was like this.

* I've installed MSSQL Express 2012 to VSRV.
* Then I've installed Veeam Backup and Replication to VSRV and pointed to existed SQL instance (which is SQL Express 2012)
* I've installed MSSQL 2016 to DBSRV and imported the famous Northwind database.
* I've backed up DBSRV.
* Tried to schema recovery and got the staging error due to SQL Server version of VSRV (I've had to install it that way because I've need to produce same error on my production environment)
* I've upgraded SQL Express 2012 to SQL Server 2016 on VSRV.
* After that, I've tried staging again. I've passed the first error (which was related to SQL Server version).

Now, about your question.

* On VSRV, I'm using Windows authentication with local admin account.
* On DBSRV, I'm using Windows authentication with local admin account.
* These two servers are not it a domain.
* I'm starting the staging process on VSRV with Veeam. Veeam asks me about SQL authentication. If I select "Use current account" (Which is VSRV local admin) I'm getting an error, of course. "Cannot resolve account for SQL Server access"
* If I select "Use the following account" and give DBSRV\Administrator password, I can proceed to next step. And I get the error I've mentioned at my first post.


So. DBSRV. I can connect with local administrator account to SSMS. Under Database -> Security -> Users I see a user. Details below:

User type: Windows user
User name: dbo
Login name: DBSRV\Administrator
Default language:
Default schema: dbo

Ths users owned schemas: none
And this users membership details: db_owner checked. Just this.

degauser
Novice
Posts: 6
Liked: never
Joined: Jan 09, 2020 5:55 am
Full Name: Sam Sepiol
Contact:

Re: SQL Server Staging Translate Error

Post by degauser » Jan 13, 2020 7:30 am

Still waiting for help...

foggy
Veeam Software
Posts: 18789
Liked: 1650 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: SQL Server Staging Translate Error

Post by foggy » Jan 13, 2020 3:59 pm

Hi Sam, please contact Veeam technical support for a closer look at your setup. Thanks!

Post Reply

Who is online

Users browsing this forum: Google [Bot], JohnW and 28 guests