måndag 17 mars 2014
Enable DPM Troubleshooting Agent and Server
I have a few problems with the current DPM implementation at Santas Workshop.
One is that I receive a strange error when trying to take a file backup on the C: Drive.
"Operation failed for C:\ on server.santasworkshop.local due to a VSS error on the DPM server. Check the volsnap events in the Windows Event Log (ID 30084 Details: Unknown error (0xd0000185) (0xD0000185))"
Checking the eventlog on both the ProductionServer and the DPM server gives absolutely nothing and searching around on the world wide internetworks gives nothing as well.
I've also tried to use the eminent tool from the Exchange team over at Microsoft called Microsoft Exchange Server Error Code Look-up ( I always use this tool to translate the 0x and -2xxx error codes), and here I drew a blank also.
So, I had to enable logging on the DPM Agent, and Ye who search shall find! a blog from blogs.msdn.com with the relevant information needed.
Create a registry DWORD at HKLM\Software\Microsoft\Microsoft Data Protection Manager
called TraceLogLevel with the value of 0x43e and restart the DPM service.
The logs will be created at the following locations.
Cut'n Paste from the blog
The DPM SERVER 2010 (or if upgraded to DPM 2012) Logs are in the C:\Program files\Microsoft DPM\DPM\temp folder.
The DPM SERVER 2012 logs are in the C:\Program Files\System Center 2012\DPM\DPM\temp folder.
The PROTECTED SERVER logs are in C:\Program files\Microsoft Data Protection Manager\DPM\temp
Just make sure that you delete the registryvalue after you are done with the troubleshooting otherwise you can fill the systemdisk.