1) Check to see if some dependent data sources have been added to the protected data source %DatasourceName;. In that case run "Modify Protection" for the protection group and consistency check for the data source by clicking the respective links below. 2) If no dependent data sources have been added to %DatasourceName;, verify if any of the dependent data sources are already getting directly protected by DPM. If this is the case, then go to the protection pane and stop protecting these data sources with the option to delete the replica. After this is done, recreate protection for %DatasourceName;. 3) If neither of the earlier options are valid, verify if the associated VSS writers are running correctly on the backend Servers. If the writer is not in a healthy state, restart the writer.
Check the library door and ensure that it is closed properly. If the door is not closed, close it and then retry this operation. ...
Check the parameters that you are passing to the cmdlet and ensure that these parameters correspond to the data source type ...
Check the parameters that you are passing to the cmdlet, and make sure that these parameters match the parameters that the ...
Check the SCSI and bus mappings of the drive to ensure that the drive is mapped correctly. If you change any of the mappings, ...
Check to see if some dependent data sources have been added to the protected data source %DatasourceName;. In that case run ...
Check to see if some dependent data sources have been added to the protected data source %DatasourceName;. In that case run ...
Check to see if some dependent data sources have been added to the protected data source %DatasourceName;. In that case run ...
Check to see if some SQL databases have been added to/or removed from the protected SharePoint farm. If this is the case, ...
Check to see if some SQL databases have been added to/or removed from the protected SharePoint farm. If this is the case, ...