Sharepoint 2016, file item restore failing

[PX IT]

Hi there,


We have a front end and back end server for hosting our internal sharepoint 2016 solution and I have been trying to figure out why Veeam does not detect the SP farm which is why i am here.

The backend server is using SQL 2014 with the sharepoint DB's in a AAG group. I have made sure both the front end and back end servers are apart of an application aware job which has run a full active already.

I have searched your help files and the following information seems interesting

Microsoft SharePoint Server

-- The server hosting the Microsoft Sharepoint database must have the Microosft Sharepoint Service running on it.
-- The server hosting the Microsoft Sharepoint database must have the Osearch VSS writer. To check a list of vss writers on the server, use the vssadmin list writers command.
-- The Osearch VSS writer must be in the Stable/No Error state.
-- The Microsoft Sharepoint farm topology must return a value other than null.

So do you recommend me install the SP service and VSS writer on the back end server? What would be the process to do this apart from actually installing SP on this server.

Further

Looking at the logs for the application aware job,

Code: Select all

[14.02.2017 02:09:28] <47> Info Backing up SqlInfo
[14.02.2017 02:09:28] <47> Info [OIB] Updating OIB, id '56cce04b-9dd2-479d-97c3-4418fab7ef40', hasSql 'False':'True'
[14.02.2017 02:09:28] <47> Info Backing up SharePointInfo
[14.02.2017 02:09:28] <47> Info [OIB] Updating OIB, id '56cce04b-9dd2-479d-97c3-4418fab7ef40', hasSharePoint 'False':'False'

Any assistance to who ever has delved into this issue in the past and solved it would be greatly appreciated.

To note i already have a support ticket open although attacking this from two angles for a quick resolution is needed.


Thanks

Mark

[Vitaliy S.]

Mark, please include your support case ID as a reference to the issue you're having.

[PX IT]

Hi Vitaliy,

Veeam Support - Case # 02050014

So far a SPSToSQL mapping in the registry has been created on the front end server although the issue still persists.


Thanks

[PX IT]

Hi Vitaliy,

What are your thoughts with this issue?

[Vitaliy S.]

Don't have anything off the top of my head. Let's see what our support team can advise in this situation.

[foggy]

So far a SPSToSQL mapping in the registry has been created on the front end server although the issue still persists.

Do you mean you've configured mapping on the SharePoint server itself? It should be configured on the backup server.

[JensM]

Hello,

it looks like we have the same problem.
We 've backed up our sharepointfarm with application aware processing enabled.
The Backupjob finished without failure, but when we open the Restore Wizzard and choose sharepoint, Veeam does not show any sharepoint content in its backed up vm's.

Has your problem been fixed? What was the solution then?
Veeam support asked us in the first step to check the vss writers on the problematic vm's.
We're missing, which writers should be running on what sharepoint role - thats something veeam could provide in his documentation.

Regards, Jens

[foggy]

Hi Jens-Moritz, have you configured SharePoint to SQL mapping in the registry?

[JensM]

Hey foggy,

yes we did. We tried the mapping with fqdn and without - but it was not solving the issue.
I thought the SQL mapping just solves the "exclemation mark problem", when opening the sharepoint explorer.

At the moment we are still wondering if there is a problem with the vss writer for sharepoint ....

Regards, Jens

[foggy]

Btw, how do you start the restore process? Are you using the Restore button on the toolbar or right-click the corresponding backup and select SharePoint option?

[JensM]

We tried several ways : The Restore Button, choosing the VM first and go to "Application Items -> Sharepoint" or even open the storage snapshot with rightclick on the backedup vm.

[foggy]

I'd ask support engineer for further assistance with VSS writers checking.