Thursday, November 4, 2010

Quick Recap of DPM 2010/SharePoint 2010 config steps:

Seems like a lot of people are seeing the DPM MetaData error when getting SharePoint 2010 set up for item level restore.  I've posted an article specifically about resolving this error, but it presupposes that the initial configuration for DPM 2010 SharePoint protection has been completed.


I've posted the initial configuration steps below:


From a command window run as administrator on your SharePoint Web Front

pushd [YourDPM Directory default c:\program files\microsoft Data Protection manager\DPM\bin]
ConfigureSharePoint.exe -EnableSharePointProtection
[provide your farm service account user and password when prompted]

ConfigureSharePoint.exe -EnableSPSearchProtection
[provide your farm service account user and password when prompted]
"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm" -o registerwsswriter
Run "vssadmin list writers" and check for any VSS writers not in "stable" state.

Restart the following services on the SharePoint Web Front End
  • Volume Shadow Copy Services
  • SharePoint VSS Writer
  • DPMRA
Build the replica in DPM

Possible causes of problems with item level restore in addition to the metadata error:
  • One of the SharePoint databases is already protected by DPM -- 
    • Protect the SharePoint Farm before configuring database protection.  The config and content databases will then become unavailable for protection for SQL Server.
  •  Item level restore is configured correctly but the catalog hasn't yet populated -- Follow these instructions to force the catalog to populate.

No comments:

Post a Comment