To troubleshoot this issue, do the following: 1) Review the System Event log for any hardware-related errors on the protected computer. 2) Run hardware diagnostic tools to verify the health of the hardware. 3) Run application-specific integrity checks to ensure logical consistency of the data. In case of a failure, recover the data from latest recovery point, and then perform an application-specific integrity check. Repeat this process with previous recovery points until you recover a logical consistent recovery point. 4) Manually create new recovery points for the data source indicated in the error. 5) Run more frequent integrity checks.
To troubleshoot this error: 1) Verify that %ServerName; is remotely accessible from the DPM server. 2) If a firewall is enabled ...
To troubleshoot this error: 1. Verify that the newly added nodes of cluster have DPM agent installed on them. 2. Run a synchronization ...
To troubleshoot this issue, do the following: 1) Review the System Event log for any hardware-related errors on the protected ...
To troubleshoot this issue, do the following: 1) Review the System Event log for any hardware-related errors on the protected ...
To troubleshoot this issue, do the following: 1) Review the System Event log for any hardware-related errors on the protected ...
To troubleshoot this issue, do the following: 1) Review the System Event logs for hardware related errors on the protected ...
To troubleshoot this issue, do the following: 1) Review the System Event logs for hardware related errors on the protected ...
To troubleshoot this issue, do the following: 1) Review the System Event logs for hardware related errors on the protected ...
To troubleshoot this issue, verify the following: 1) The data source is online. 2) The data source is not in a restoring ...