It took us a while to figure this out, so I'm posting this in case it's helpful for someone out there. Plus, I have a question...
DPM gave the following error for one of our file servers:
Description: The replica of Volume D:\ on <servername> is inconsistent with the protected data source. Number of files skipped for synchronization due to errors has exceeded the maximum allowed limit of 100 files on this data source (ID 32538 Details: Internal error code: 0x809909FE)
Recommended action: Review the failure errors for individual files from the log file \\?\Volume{8492c150-f195-11de-a186-001cc4ef89a0}\B1E9D373-2C03-464E-A472-99BC93DB1E2A\FailedFilesLog.txt and take appropriate action. If some files fail consistently, you can exclude the folders containing these files by modifying the protection group or moving the files to another location.
So, how do you actually open the FailedFilesLog.txt file shown in this DPM alert? What is this path referring to? Well, this is the mount point for the protected server's replica volume on the DPM server, which is mounted under \Program Files\Microsoft DPM\DPM\Volumes\Replica\servername\File System. Here you'll see the mount points for all of the server's protected volumes. However, if you try to open one of these mounted volumes in Windows Explorer, you'll get Access Denied, even if you have administrator rights. (If someone knows of a way around this, please let me know). As a workaround, you can access this mounted volume in an elevated command prompt. Steps:
- Open an Administrator Command Prompt
- Type mountvol <AnyAvailableDriveLetter>: \\?\Volume{VolumeGUID}
- Example: mountvol m: \\?\Volume{8492c150-f195-11de-a186-001cc4ef89a0} Note that we're only using the first part of the path to the FailedFilesLog.txt file given in the DPM alert, starting from \\? and ending after the } character.
- Next, type m: to change to the newly mounted m: drive.
- Then type cd B1E9D373-2C03-464E-A472-99BC93DB1E2A This is actually a folder name so we're just going into this folder.
- Finally type dir and you should see the FailedFilesLog.txt file. This file can be copied to another location where it's easier to use (i.e. in Windows Explorer).
- Be sure to unmount this volume when you're done by typing mountvol m: /d in the command prompt. (Mountvol reference: http://technet.microsoft.com/en-us/library/cc772586(WS.10).aspx.)
What a pain, eh? But at least by reviewing the FailedFilesLog.txt file you can determine which files or folders caused the sync to fail and thus take action accordingly.
Now, here's my question: Where is that registry key that lets me adjust the limit of 100 files that DPM allows to be skipped before it fails the replica? Hopefully someone out there will tell me. I know this can be done because Kapil Malhotra said so in this post: http://groups.google.com/group/microsoft.public.dataprotectionmanager/browse_thread/thread/a179fa30fb50c9b0/e9a348f2a9386063?lnk=raot.
Also, does anyone know what the internal error code 0x809909FE means in this alert? Knowing this my help us determine what caused these files to fail. Interestingly, in the FailedFilesLog.txt file, it gave a different error code next to each failed file: 0x80070002.
-Taylorbox
- Moved by Praveen D [MSFT]Owner Monday, July 19, 2010 6:19 AM Moving DPM File Protection Forum (From:Data Protection Manager)
Other recent topics
