Hi all,
We have a DPM 2012 R2 server (version: 4.2.1273.0) installed on a Windows Server 2012 Standard (not R2). We try to backup our virtual file server which is also a Windows Server 2012 Standard (not R2).
This file server has a local C: and D: drive and an E: drive connected from SAN with Windows deduplication turned on.
We can backup everything on this server (System State, Bare metal, C: and D: drives) except the E: drive.
The problem is, when we create a protection group and add this server to it, the first replica is successful for all components (even E: drive) but the following synchronizations failing for the deduplicated E: drive. If i run a consistency check, it seems
it’s backing up, because ont he Monitoring tab I can see that there is a data transfer. But it always ends up with replica inconsistent.
I have this alert in DPM console:
DESCRIPTION:
The replica of Volume E:\ on FILESERVER.COMPANY.LOCAL is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery
points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
RECOMMENDED ACTION:
Review the failure errors for individual files from the log file \\?\Volume{ebad65e7-fcf2-13e4-962d-001ec9ee5638}\e3866ced-d582-263a-a326-a6aabdc8f361\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.
I’ve tried to access FailedFilesLog.txt but I got „Access Denied” error. I’ve tried to open it by mounting the volume. I was able to browse the System Volume Information, but when I try to navigate into the replica folder the comes the „Access Denied” error
message. (I ran command prompt as an administrator)
Thanks for any help.
Kind regards,
Dvijne