Microsoft Office Tutorials and References
In Depth Information
If you do encounter any errors the first step is to search http://support.
microsoft.com for more information on the error. If you cannot resolve it
there you may need to contact Microsoft support.
• Make sure your DPM server and the protected computer with the error can
communicate. From the DPM server ping the protected computers. On the
protected computer ping the DPM server. Here is an example of the ping
Pinging BUCHDPM.buchatech.com [192.168.1.17] with 32 bytes of
Reply from 192.168.1.17: bytes=32 time=26ms TTL=128
Reply from 192.168.1.17: bytes=32 time=5ms TTL=128
Reply from 192.168.1.17: bytes=32 time=2ms TTL=128
Reply from 192.168.1.17: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.1.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 26ms, Average = 8ms
Doing this will help you verify that the name resolution (DNS) is working.
Without name resolution the DPM server and protected computer would not
be able to communicate.
• Check the DPM Monitoring tab for alerts and errors. The information on
this tab will tell you what the issue is, it will give you an error ID that you
can look up on TechNet (the link to this site is coming up in the resources
section), and it will sometimes give you potential ixes to whatever issues
are occurring. This is especially helpful when you have issues with protected
• Check the event logs on the DPM server and the protected computer
around the time when the job failed. This can help you identify issues with
the operating system, other system issues, or application-specific issues.
You can check this in the Windows Event Viewer under: Event Viewer |
Applications and Services | DPM Alerts .