Explorer for Microsoft SQL Server Requirements?

[imiddleton]

I installed v8 a couple weeks ago and I am now testing transaction level restores with the SQL Explorer.

After I select "Restore to a point in time" and check "Perform restore to the specific transaction" and click Next, I get the following error on the "Fine-tune the restore point" page of the wizard: "Cannot find SQL Server service registry entry."

Where is Veeam looking for the SQL Server service registry entry? On the SQL Server, or on the server that Veeam is running on? Does remote registry need to be enabled on the SQL server?

Any help would be appreciated. Thanks!

[Vitaliy S.]

Are you using remote or local SQL Server with Veeam B&R?

[imiddleton]

It was defaulting to the remote SQL server.

I just changed the SQL server to the local under Options on the SQL Explorer window and that seems to work.

Should it work with the remote server, or do you always have to use the local?

[Vitaliy S.]

I know that this is a requirement for Explorer for SharePoint, but cannot confirm that it is also applicable for SQL Server now (will it do it Monday). Do you have a remote registry enabled on the remote SQL Server?

[ianikigorevich]

You should use local intance of SQL. The full functionality of VeeamExplorerForSQL, staged on the remote SQL instance, is in testing now, and will be available in the next version.

Thank you!

[CurtLeCaptain]

Is this documented somewhere saying that we should use local SQL? What does this do for larger shops that prefer using a remote SQL server for this purpose, what are workarounds? Installation of another SQL server locally on the Veeam box, reinstallation of Veeam with a local SQL instance? Just looking for guidance as this could be a pretty big stopping point toward switching to Veeam doing our SQL backups.

[Vitaliy S.]

As a workaround you can install, for example, SQL Server Express on the backup server (no need to use it with your Veeam B&R server) and then specify it as a staging server.

[CurtLeCaptain]

Fantastic. Thanks for that information, I'll use that as a workaround. Is there a specific version that Veeam will expect? (2012, 2014, 2008 R2?)

[veremin]

What version does the SQL server you're backing up have? Thanks.

[Vitaliy S.]

Version should not be lower than the version you're backing up with SQL backup jobs. Thanks!

[CurtLeCaptain]

We've got a mix of 2008, 2008 R2, and 2012 here.

[veremin]

Then, stick to the highest version - 2012 in your case. Thanks.

[aimaraa]

HI All,

Have anybody seen the issues with the Veeam Explorer for SQL Server while trying to restore a point in time and using specific transaction?
If I tick "Perform restore to the specific transaction" option and click next, I will get the error "Cannot find SQL Server service registry entry".



Is there any fix for that?

Case ID: 00733055

[aimaraa]

I forgot to add that Veeam version is 8.0 and last patch is installed.

[veremin]

Hi, Aimar,

Are you using remote SQL server with VB&R by any chance?

Thanks.

[aimaraa]

Hi, Aimar,

Are you using remote SQL server with VB&R by any chance?

Thanks.

Yes indeed, i have Veaam SQL DB running in separate virtual server.

I see from previous posts that i cant have remote SQL, it is pretty big bummer. I will try this workaround, unless its should have been fixed with latest patch?

[veremin]

No, it has not been fixed in the latest patch. Thanks.

[aimaraa]

No, it has not been fixed in the latest patch. Thanks.

Is there any info about ETA for this fix? If its in the near future, i would just ignore it for now.

[veremin]

No ETA at the moment. We will update the topic, as soon as we have more information, though.

[Andrew.L]

Hi, can anyone pls confirm for me, that this is probably my issue when trying to perform SharePoint restores, via my Veeam B&R server (which runs the native SQL 2K12 Express)?
I've been able to perform a 'windows files' restore of the SQL server hosting the SharePoint DBs, at which point I choose 'Application Items\SharePoint items' from Backup Browser, which launched 'Veeam Explorer for Microsoft SharePoint'. The issue I then have is that not all of the DBs mount.
From some research (which has led me here) it seems that SQL express isn't able to mount the DBs over 10GB in size, and trying to configure the Veeam Explorer for MS SharePoint to use a remote SQL server is throwing the 'cannot find sql server registry entry' error when trying to mount the DB.
(I'm using Veeam B&R v8).

[foggy]

Andrew, you should use local staging SQL server for Sharepoint restores.

[Andrew.L]

Andrew, you should use local staging SQL server for Sharepoint restores.

Sorry foggy, as I mentioned in my post, I can't use the local SQL server for staging, as half of the SharePoint DBs I need to browse are over 10GB (and the local Veeam SQL instance is using the default express version).

[foggy]

The SQL upgrade is required for using Veeam Explorer for SharePoint to restore from these databases.

[Andrew.L]

The SQL upgrade is required for using Veeam Explorer for SharePoint to restore from these databases.

foggy, the option of leveraging a remote SQL server to browse the restored SharePoint dbs is a feature of Veeam, obviously to allow for situations where the local SQL instance on the Veeam B&R server isn't capable of doing so. Suggesting a SQL upgrade simply isn't acceptable. Btw, I have an active case logged with Veeam for this right now, and they've acknowledged there's an issue/bug and their Devs are working on a fix.

[foggy]

foggy, the option of leveraging a remote SQL server to browse the restored SharePoint dbs is a feature of Veeam

It's not yet. As it is stated above, remote SQL staging server support is still in development, so currently you have to use local SQL Server.

Btw, I have an active case logged with Veeam for this right now, and they've acknowledged there's an issue/bug and their Devs are working on a fix.

Could you please share the case ID? Thanks.

[Andrew.L]

Btw, I have an active case logged with Veeam for this right now, and they've acknowledged there's an issue/bug and their Devs are working on a fix.

Could you please share the case ID? Thanks.

00738548

[foggy]

Thanks, it's not actually a bug and fix but rather just adding support for remote staging SQL server, which is currently being implemented to be included in one of the next versions (just as it was already mentioned here).

[Andrew.L]

Thanks, it's not actually a bug and fix but rather just adding support for remote staging SQL server, which is currently being implemented to be included in one of the next versions (just as it was already mentioned here).

Thanks foggy.
Could you please do me a favour, and provide a link/reference to where it suggests that the remote staging SQL is an experimental feature only?
Thanks again.

[tsightler]

For Sharepoint: http://helpcenter.veeam.com/backup/80/e ... erver.html
Specifically this quote:

Remember that this must be a local server (the one where Veeam backup server is installed) and must meet all requirements specified above.

For SQL Explorer: http://helpcenter.veeam.com/backup/80/e ... mreqs.html
Specifically this quote:

Remember that your staging system must be a local instance of the SQL server (the one where Veeam backup server and Veeam Explorer for Microsoft SQL Server are installed) and must have the same or later version as the original SQL server.

The SQL server selection dialog allows you to select a specific instance if you have multiple SQL instances installed on the local Veeam server, but you cannot currently select a remote SQL server (well, you can, but it won't work).