DPM 2012 : Sharepoint 2010 en ILM (Item Level Recovery) Running on SQL Cluster fails with :”DPM was unable to attach the database to the SQL Instance SERVER\INSTANCE”

November 30, 2012 at 1:47 pm in backup, dpm, DPM 2012 by Kenny Buntinx [MVP]

 

At my customer today , we were upon the first tests on our DPM 2012 platform protecting a SP 2010 farm. The protection groups are working perfectly , however, when trying to recover a Sharepoint item (a jpg file) we are facing some problems. here is a sample recovery session:

  • start the recovery wizard on the document
  • specify the SQL cluster instance as the staging SQL server
  • specify a temporary folder on the SQL cluster, which is already included in the cluster dependencies
  • specify a temporary folder on the WFE.

The recovery process ends with failure, displaying this warning on the DPM console: "DPM was unable to attach the database to the SQL Instance SERVER\INSTANCE. Cannot use file \\DPMSERVER\WSSILRShare_{guid}\local-replica-path-to-mdf for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the sql server does not have a dependency on it (ID 32000 Details :Unknown)"

clip_image002

Solution :

******************The answer below is not right for the error code – I am still investigating why this is not fixed *******************************

******************I will update when the right solution is fixed *******************************

There is a known limitation when using optimized item level recovery (ILR) for Sharepoint 2010 that uses clustered SQL Servers. The workaround is to perform a non-optimized recovery.  Please add the following registry key and try a new recovery.

To disable Optimized ILR completely, use the following registry key on the DPM 2012 server:

Key HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\SharePoint
Value: DisableOptimizedILR
Data:0x1
Type: DWORD

******************The answer below is not right for the error code – I am still investigating why this is not fixed *******************************

Hope it Helps,

Kenny Buntinx

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest