1) Run chkdsk on the affected volume and then run synchronization with consistency check. 2) If running chkdsk does not solve the problem, and the server indicated above is a protected server (and not the DPM server), consider deleting this file from the source and then running synchronization with consistency check.
Review the list of failed files here and exclude them from backup, or address the individual errors in the log. Then retry ...
Review the log files on %ServerName;: windir emp\msdpm*.log and take appropriate action. Retry the operation, and if the ...
Right click to change auto protection status. When instance is Auto Protected any new database that is found will be automatically ...
Run chkdsk on the affected volume and then run synchronization with consistency check. 2) If running chkdsk does not solve ...
Run chkdsk on the affected volume and then run synchronization with consistency check. 2) If running chkdsk does not solve ...
Run chkdsk on the affected volume and then run synchronization with consistency check. 2) If running chkdsk does not solve ...
Run SQL Configuration tool on the computer running SQL Server to change the account for the services. Then run the program ...
Run the following command at the command prompt to start the DPM Troubleshooting Console manually: %CommandlineArgument; ...
Run the following command at the command prompt to start the DPM Troubleshooting Console manually: %CommandlineArgument; ...