Diagnostic Process for Request Tracking and Error Tracing
Letzte Aktualisierung: April 2010
Betrifft: System Center Data Protection Manager 2010
This topic explains the process for diagnosing request tracking and error tracing for System Center Data Protection Manager (DPM) 2010.
Request Tracking
Every trace statement has a log task ID that DPM logs in the agent traces. The log task ID is a globally unique identifier (GUID) that DPM generates for every task in the DPM engine. The log task ID is sent as a parameter in every command to the agent. There is full tracking for each task in the traces, which helps isolate traces for the job you want to trace. This is especially helpful when there are many data sources that you are protecting.
Request Tracking Tuning Feature
The request tracking tuning feature is available in the DPM engine, the DpmRA service, and other agent binaries. The feature is built into the binaries and it is always ON.
Error Tracing
Log error traces are put into a log file. These fixed sized error logs are retained for a specific amount of time. The log file is written in normal text and is readable by the administrator. The diagnostic information from these files is logged and can be collected by the Microsoft Platform Support Reporting utility (MPSRPT) from the user's computer.
The log file helps administrators and Customer Service and Support (CSS) with firsthand information instead of the error code that appears in DPM Administrator Console. This helps categorize the failures more efficiently, and therefore reduces turnaround time.
Additionally, since DPM logs as much diagnostic information as possible along with the API that has failed, the diagnostics and investigation can start before the user returns with a verbose log.
Error Tracing Tuning Feature
The error tracing tuning feature is built into the DPM engine, the DpmRA, DPMLA, DPMAC, DpmBackup, and DpmWriter services. It is always ON and collects TRACE_ERROR level traces into the log file by default.
The following table shows how to tune the various parameters that drive the tuning feature.
| Parameter | Overriding Registry Key | Default Value | Possible Values |
|---|---|---|---|
Trace level |
TraceLogLevel |
TRACE_ERROR |
All valid trace level flag combinations |
Location |
TraceLogPath |
DPM install Path |
A valid existing folder path |
Max size of each file |
<binary>TraceLogMaxSize |
5 MB |
A file size (total disk space consumed for this binary’s log = size * number of files to retain) |
Max number of files to retain |
<binary>TraceLogMaxNum |
30 |
Any non-negative number |
<binary> = MSDPM (for engine), DPMRA (for RA), DPMLA (for LA), DPMAC (for AC), DpmBackup (for DPM backup), DpmWriter (for DPM writer).
Note the following:
The root path for the registry keys is HKLM\Software\Microsoft\Microsoft Data Protection Manager.
The trace level and trace log location setting is global across all binaries.
The current log file number is tracked in the registry key HKLM\Software\Microsoft\Microsoft Data Protection Manager: <binary>TraceLogNextNum (DWORD). This is an internal registry key and we recommend that you do not manually modify it.