I'm trying to restore a subsite from a site collection using SMSP 6 and I'm getting the following error log:
Path:Farm(Farm)\Microsoft SharePoint Foundation Web Application\SharePoint - spdev.domain.com443\DomainSP_Content1_sharepointdbsrv-dev,Status:Successful; Path:https://spdev.domain.com,Status:Successful; Path:helpdesk,Status:Failed; Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED));
I've made sure to give appropriate access to agent service account.
I've read over numerous articles on the NOW about which service accounts need which permission at either a SharePoint level and/or a SQL level and/or OS level. I'm curious which access you've given your agent service account.
Either set the smsp service account on the application pool or change the credential for the smsp agents active on the sharepoint servers. For my company it was easiest/best to change the credentials on the smsp agents and use the farm admin account used to install and configure sharepoint. After the change restores work.
I found out the solution to my problem with restoring individual items while overwriting existing. The trick was to set the SnapManager for Sharepoint Agent service to run as the same user that the SharePoint 2010 Timer service is running as. In my case, when I installed SQL and then SharePoint, I used sql2008 as the service account for the SQL 2008 installation and sp2010 for the Sharepoint 2010 service account. Through the SMSP interface, Control Panel -> Control Service -> Agent Monitor (tab) -> Configure.
Looks like that KB is what should have worked but as a talked to support they said a few instances have been coming up to where there is a hotfix that needs to be applied. Support applied it and now the restores work just fine.
Facing same Issue here... restore works when using the FarmAdmin itself... but policies at this customer forbid to use the FarmAdmin itself, instead we must use a User in the FarmAdmin Group... so the workaround in the netapp KB is not a solution...
Can you give us the Q Number of the Microsoft Hotfix that you applied? As far as I understood the root cause of this problem is that somehow the permissions for a User in the FarmAdmin group within sharepoint are not correctly applied... would this Hotfix fix that?