To resolve this issue, verify the following: 1) The protected SharePoint Service Provider (SSP) is online and running. 2) The WSSCmdletWrapper DCOM component is configured correctly on the front-end Web server hosting the protected farm. For more information, see the System Center 2012 R2 DPM Operations Guide. 3) Retry the operation and verify that no other application or process is trying to resume the SSP crawl during backup.
To resolve this issue perform one of these actions: 1) Migrate the datasource to use different volumes using MigrateDatasourceDataFromDPM.ps1. ...
To resolve this issue, do the following: 1) Turn off the SharePoint VSS writer on the front-end Web servers on which you ...
To resolve this issue, specify the backup or consistency check window for a protection group that has short term protection. ...
To resolve this issue, verify the following: 1) The appropriate SQL Server VSS writers are enabled on the computers hosting ...
To resolve this issue, verify the following: 1) The protected SharePoint Service Provider (SSP) is online and running. 2) ...
To restrict where the end users can put the recovered files on the SQL Server, specify a path below. To allow end users the ...
To review the list of computers that DPM has not backed up, click View Error Details and take appropriate action.To modify ...
To run DPM Setup Pre-Requisite Checker, you must accept the Microsoft Software License Terms. These license terms apply for ...
To set a new retention policy you'll need to stop online protection for all data sources in the group and then add online ...