Backing up Sharepoint 2010 in Veeam v7

[ejleipold]

Since upgrading to v7, I'm getting a warning when backing up my Sharepoint 2010 (Win 2008 R2 SP1) VM.

Error is:

Failed to inventory guest system: Cannot get host information. Cannot collect host info. Microsoft SharePoint farm topology collector process is failed with exit code -1 Win32 error:The operation completed successfully. Code: 0

Any ideas?

[Vitaliy S.]

Hello Evan,

Please include the Veeam support case ID for this issue. As explained when you click New Topic, support case ID is required when posting about technical issues.

Thank you!

[HussainMahfood]

I have same issue as above.

[ejleipold]

It doesnt seem to stop the VM from backing up, so I had'nt bothered logging a job yet, was just curious if someone else had seen it too. I've actually just setup a whole new backup job so I'm going to run that and see how it goes, will probably log a support request after that.

[Gostev]

What fails here is the new process that collects SharePoint topology information to streamline item-level restores. This process is not essential neither for backup, nor for actual item restore (you can still restore SharePoint items if it fails, just takes a few more clicks). Nevertheless, we would like to investigate the issue through the logs, so that we could fix it with the patch.

[ejleipold]

No worries, I'll log it

[HussainMahfood]

I logged a case regard this. Case # 00431386

[Gostev]

Thank you.

[ejleipold]

Case 00431404

[sf4692]

same problem here since upgrade to V7, using SBS 2011 (which is more or less Server 2008 R2 as u surely know), Case ID:

Case # 00430412

[duliere]

Hi, I've the same issue with a SharePoint 2013 farm

kind regards, Didier

[martynuk]

Same problem. Case #: 00432816

[Emmer]

Just give the user you configured for guest processing access to your sharepoint config db.
It pops up in the eventlog of the target server.

[vromster]

Just give the user you configured for guest processing access to your sharepoint config db.

Thanks, great advice. Do you (or Veeam support) know which permissions are necessary?

[tomas.olsen]

What kind of permissions and roles should the users specified for VSS have on the sharepoint config db??
And does the user need to have access to other sharepoint databases other then the config db??

[Emmer]

i'm sorry, i haven't had time to check the least privilege, i'm still running it in a testing environment and at the moment the backup service user is sa on the db server.
In case nobody has had the time to test this i'll check it out tomorow and get back here with the list, although i'm thinking read only with a bit of tweaking to possibly truncate, should be enough.

[Emmer]

Awesome

I think the whole thing is fixed then

[Dima P.]

I believe my assumption that account used for working with Veeam Explorer for SharePoint requires membership in the sysadmin fixed server role on the staging Microsoft SQL Server is still valid. But just to be sure - I will double check that.

[tomas.olsen]

Thats correct, member of sysadmin server role will do the trick. Tried it and it worked. It is also specified in the user guide (if one would just take a few minutes and read it )
But I find it odd that the user needs sysadmin role of the entire sql server.
The backup did perform successful, but I would be happier if I could use a role with less permissions, and maybe just a few of the databases.

[ejleipold]

Nice, I'll try that today.

Veeam support didnt know that, they basically said it was because they hadnt managed to full get sharepoint farm topology to work for Veeam explorer, which they were now aware of and were going to be resolving the issue in the next version. I asked if there was a way to suppress the warning (because I'm a bit crazy OCD and I like my green ticks) but apparently you can't.

I'll see how your solution goes.

[tomas.olsen]

Might be slight embarrassing if support didn't even know what was in the user guide

Anyway, you will get your green ticks if the user specified for VSS has sysadmin role of the sharepoint SQL server.
AIR on the other hand was not successfull. we will se how it turns out.

[ejleipold]

Yaaay green ticks!

Thanks, I'll see how it goes overnight.

[Dima P.]

Yes, it is indeed in the user guide, the problem is - that it in the requirements for the SharePoint Explorer which is originally used for restore operations - so this could be a bit confusing in such case when we are talking about backup procedures. Honeslty it confused me too - as first I just post here the quote from the user guide

Thank you for heads up, it has already been taken care off!

[ejleipold]

Yep, that works, thanks Tomas!

[kte]

same issue here after updating to veeam 7 , I guessi because he knows sharepint now

[ph1l1pp]

I'm having the same problem. It is a SBS server where the sharepoint services and its database are disabled. Veeam still tries to connect to it. Is there a way to disable sharepoint processing in veeam but leave exchange and other application aware processing enabled?

[kte]

does it work with SQL authentication only DB's

[veremin]

Is there a way to disable sharepoint processing in veeam but leave exchange and other application aware processing enabled?

Nope, it's not possible, as this option is set on a VM level, not on an application one. Thanks. 

[smarivoet]

small issue on this matter.
I have a few external-facing sharepoint-severs with some sql-servers.
To keep things a bit secure we are only using sql-authentication on the sql-server.

Isn't there an option to enable instead of a domain account an sql account that takes care of the sql-servers/databases but keep the domain user for VSS?

[foggy]

Isn't there an option to enable instead of a domain account an sql account that takes care of the sql-servers/databases but keep the domain user for VSS?

If you want to use "application-aware image processing", you need to specify an account with local admin privileges on the VMs being processed and there is no way to specify separate accounts for different services inside VM guest OS.