none
DPM 2016 UR2- files fail to synchronize but log file is empty RRS feed

  • Question

  • After installing UR2 (yippee) I continually get this type of error during sync of my two large deduped volumes:

    Affected area: F:\
    Occurred since: 2/9/2017 5:30:56 PM
    Description: DPM could not back up some of the required files for this data source. This could be caused by intermittent failures, or by a file type that is unsupported. If this backup is for a deduplicated volume, then some or all of the deduplicated files might not be recoverable from this recovery point.
    Number of files that failed to synchronize: 34
    During the next synchronization, DPM will try to back up these files again. (ID 32526)
     More information
    Recommended action: 
     For a list of files that could not be backed up, review the log. If any of the deduplicated metadata files could not be backed up, then run Consistency Check to make sure that the next recovery point is suitable.
     View failed files log
    Resolution: To dismiss the alert, click below
     Inactivate

    On one of the volumes, the fail count is consistently 34 files and on the other it's consistently 54 files. I do NOT get this error on EVERY sync, however.

    When I click on the "view failed files log" link it opens a text file, but it's blank.  How do I figure out what is failing and then fix this issue or verify that it isn't an issue after all?

    Thx,

    DML


    DLovitt




    Friday, February 10, 2017 12:52 AM

All replies

  • Hi,

    I don't know why the failedfileslog.txt is empty and that will make it harder to see what files were affected and the reason why.  You can try looking on the protected server at the C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\DPMCurr.errlog after you get the alert and there should be some details abut the files that could not be backed up and the error code.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, February 10, 2017 8:37 PM
    Moderator
  • I get a bunch of these entries in that log:

    3324 15F0 02/10 20:46:48.024 18 fsutils.cpp(3225)  23B25DEF-B952-4DEE-B4EA-56E8224ED7EC WARNING Failed: Hr: = [0x80070057] : GetFileHandleById failed to open file, frn:0x015B000000013FBC
    3324 15F0 02/10 20:46:48.024 18 fsutils.cpp(3225)  23B25DEF-B952-4DEE-B4EA-56E8224ED7EC WARNING Failed: Hr: = [0x80070057] : GetFileHandleById failed to open file, frn:0x00040000004F02A4
    3324 15F0 02/10 20:46:48.024 18 fsutils.cpp(3225)  23B25DEF-B952-4DEE-B4EA-56E8224ED7EC WARNING Failed: Hr: = [0x80070057] : GetFileHandleById failed to open file, frn:0x00040000004F02A4
    3324 15F0 02/10 20:46:48.024 18 fsutils.cpp(3225)  23B25DEF-B952-4DEE-B4EA-56E8224ED7EC WARNING Failed: Hr: = [0x80070057] : GetFileHandleById failed to open file, frn:0x0070000000013FB7
    3324 15F0 02/10 20:46:48.024 18 fsutils.cpp(3225)  23B25DEF-B952-4DEE-B4EA-56E8224ED7EC WARNING Failed: Hr: = [0x80070057] : GetFileHandleById failed to open file, frn:0x0070000000013FB7

    followed by:

    3324 30EC 02/10 20:46:50.865 18 usnchangeiterator.cpp(671) [0000000433628E90] 23B25DEF-B952-4DEE-B4EA-56E8224ED7EC NORMAL Fixup needed for filePath : \\?\Volume{607a5113-15ac-4776-b708-1af3b33cf453}\System Volume Information\Dedup\ChunkStore\{9CC5E9AF-2519-46AB-B9D9-36B87FAAF73A}.ddp\COW\ and fileSpec : *

    But everything else looks like gibberish in there to me.

    TIA!

    DML


    DLovitt


    Friday, February 10, 2017 9:07 PM
  • Hi,

    I don't know why the failedfileslog.txt is empty and that will make it harder to see what files were affected and the reason why.  You can try looking on the protected server at the C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\DPMCurr.errlog after you get the alert and there should be some details abut the files that could not be backed up and the error code.


    Hi Mike, same problem here. There is the log from DPM:

    fsutils.cpp(150)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    Dedup Status enabled on the machine
    writeriterator.cpp(369)    [000002C6AB8224F0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    CFileWriterIterator::SetVolumeInfo Dedup support found
    writeriterator.cpp(372)    [000002C6AB8224F0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    Restoring Dedup volume. Checking if target volume is Empty..
    writeriterator.cpp(375)    [000002C6AB8224F0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    Restoring Dedup volume. Checking if target volume is NTFS..
    fsutils.cpp(4901)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    NTFS volume Detected. Volume = [\\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\]
    fsutils.cpp(4064)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : HRESULT_FROM_WIN32(dwError)
    fsutils.cpp(4064)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : HRESULT_FROM_WIN32(dwError)
    basewriterbackuphelper.cpp(134)    [000002C6AACC0DC0]    84966526-9BF1-44F5-8B09-14D323ABB685    NORMAL    SetOperationType(0)
    fsutils.cpp(4064)        84D3A512-EF99-4DD1-89CB-E79AE20EA05C    WARNING    Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : HRESULT_FROM_WIN32(dwError)
    fsutils.cpp(4064)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : HRESULT_FROM_WIN32(dwError)
    fsutils.cpp(4064)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : HRESULT_FROM_WIN32(dwError)
    fsutils.cpp(4064)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : HRESULT_FROM_WIN32(dwError)
    fsutils.cpp(1852)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    GetVolumeHandle Volume Path = \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}
    fsutils.cpp(1852)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    GetVolumeHandle Volume Path = \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}
    fsutils.cpp(1852)        98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    GetVolumeHandle Volume Path = \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}
    mtffixuplist.cpp(367)    [000002C6AAB63180]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] SetNextBuffer() failed on file \\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW
    continueonfailurehandler.cpp(571)    [000002C6AAA24BD0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] CContinueOnFailureHandler: (dsmStatus:3, Logical File File Path:\\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW, Physical file Path: \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\768040ac-4330-4a6e-81b7-2c5446af82bb\Full\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW, File Info Type:0, FileId: 6755399441431407)
    mtffixuplist.cpp(367)    [000002C6AAB638C0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] SetNextBuffer() failed on file \\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00010000
    continueonfailurehandler.cpp(571)    [000002C6AAA24BD0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] CContinueOnFailureHandler: (dsmStatus:3, Logical File File Path:\\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00010000, Physical file Path: \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\768040ac-4330-4a6e-81b7-2c5446af82bb\Full\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00010000, File Info Type:0, FileId: 3377699720904323)
    mtffixuplist.cpp(367)    [000002C6AAB63C60]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] SetNextBuffer() failed on file \\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00020000
    continueonfailurehandler.cpp(571)    [000002C6AAA24BD0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] CContinueOnFailureHandler: (dsmStatus:3, Logical File File Path:\\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00020000, Physical file Path: \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\768040ac-4330-4a6e-81b7-2c5446af82bb\Full\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00020000, File Info Type:0, FileId: 281474977087117)
    mtffixuplist.cpp(367)    [000002C6AAB63180]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] SetNextBuffer() failed on file \\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00030000
    continueonfailurehandler.cpp(571)    [000002C6AAA24BD0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] CContinueOnFailureHandler: (dsmStatus:3, Logical File File Path:\\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00030000, Physical file Path: \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\768040ac-4330-4a6e-81b7-2c5446af82bb\Full\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00030000, File Info Type:0, FileId: 844424930508424)
    mtffixuplist.cpp(367)    [000002C6AAB638C0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] SetNextBuffer() failed on file \\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00040000
    continueonfailurehandler.cpp(571)    [000002C6AAA24BD0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] CContinueOnFailureHandler: (dsmStatus:3, Logical File File Path:\\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00040000, Physical file Path: \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\768040ac-4330-4a6e-81b7-2c5446af82bb\Full\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00040000, File Info Type:0, FileId: 5629499535649031)
    mtffixuplist.cpp(367)    [000002C6AAB63180]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] SetNextBuffer() failed on file \\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00050000
    continueonfailurehandler.cpp(571)    [000002C6AAA24BD0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] CContinueOnFailureHandler: (dsmStatus:3, Logical File File Path:\\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00050000, Physical file Path: \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\768040ac-4330-4a6e-81b7-2c5446af82bb\Full\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00050000, File Info Type:0, FileId: 1688849861832557)
    mtffixuplist.cpp(367)    [000002C6AAB63180]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] SetNextBuffer() failed on file \\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00060000
    continueonfailurehandler.cpp(571)    [000002C6AAA24BD0]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    WARNING    Failed: Hr: = [0x80070057] CContinueOnFailureHandler: (dsmStatus:3, Logical File File Path:\\?\Volume{4d458760-52a7-45a9-b0ca-416bcac66da3}\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00060000, Physical file Path: \\?\Volume{04e4dec6-246d-4b4a-ab32-584c2327257f}\768040ac-4330-4a6e-81b7-2c5446af82bb\Full\System Volume Information\Dedup\ChunkStore\{F88B19AD-3F70-4DC1-8A2C-204288EEF426}.ddp\COW\00060000, File Info Type:0, FileId: 2251799815296144)
    dsmreceiversubtask.cpp(192)    [000002C6ABC9B960]    98D1DE82-F034-4202-AC73-9DA7092ADFD3    NORMAL    End of data...Closing MTFRead

    File server is WS 2012 R2 and dedup is enable on the backuped volume.

    Wednesday, February 15, 2017 1:38 PM
  • Hello

    Weighing in because I have just upgraded to DPM 2016 UR2 and seeing the same error suddenly.

    Large deduped volume on a 2012 R2 File server, Backup server is 2012 R2 (Soon to be upgraded to Server 2016) DPM 2016 U2 with Azure Backup agent 2.0.9026.0.

    0x80070057
    \\?\Volume{00e5836a-0010-41d3-9079-1d668f0b4c99}\System Volume Information\Dedup\ChunkStore\{30926865-AE09-4FB0-BD65-C7C8E17AA633}.ddp\COW\00140000

    This is inconsistent but seems to be every second sync will bring up this warning.
    • Edited by PCAUII Monday, February 27, 2017 5:42 AM additional info
    Sunday, February 26, 2017 10:33 PM
  • Same issue here:

    DPM 2016 UR2 ond Windows Server 2016 all updates.

    PS = Win 2012R2 with DeDup enabled

    regards

    /bkpfast


    My postings are provided "AS IS" with no warranties and confer no rights

    Wednesday, March 22, 2017 11:03 AM
  • Same issue here. Please fix this because an empty log file is useless when trying to troubleshoot!!
    Monday, March 27, 2017 1:51 PM
  • HI, Thanks all for reporting this, I have opened a code review bug for the product group to investigate and see if this is something that can get addressed in a future update rollup.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, March 28, 2017 8:49 PM
    Moderator
  • Hi Mike,

    Thanks for looking into that :) But are you only looking into that FailedFiles.log is empty?

    Or also the reason for the bug that produces these errors on several DeDuped fileservers. In my case on DPM 2012R2 UR12. I see others above have same problem:

    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\000a0000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00030000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00080000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00060000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00040000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00070000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00090000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00010000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00020000
    0x80070057 
    \\?\Volume{2e2a884f-50e7-4287-8ba9-3dd37a03e5bd}\System Volume Information\Dedup\ChunkStore\{969100CD-64C6-46E0-87D7-532169618B2A}.ddp\COW\00050000

    Regards Christian

    Wednesday, March 29, 2017 3:12 PM
  • Hi,

    We will look into both conditions.  It could be we don't add those to the failedfileslog.txt because they are dedup files under System Volume Information folder which should not be messed with.  The error 0x80070057 is what needs to be investigated in more detail and see what is causing that.  If they fix that then the failedfileslog.txt won't be needed for that specific condition.

    UPDATE:  It looks like they fixed the issue(s) and should make it in UR4.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.



    Wednesday, March 29, 2017 6:34 PM
    Moderator
  • is there a hotfix for this issue or do we have to wait for UR3?  
    Friday, April 28, 2017 3:23 PM
  • I am seeing a very similar issue with DPM 2012 R2 UR 12. Protecting a 2012 R2 file server volume with deduplication in place. It's consistently generating an error stating DPM could not back up some files. In my case the Failed Files log is populated. All 18 files have the 0x80070057 error and are all ChunkStore files. Such as:

    0x80070057
    \\?\Volume{c56d21c0-eb56-4ca6-a5d6-c1244e247667}\System Volume Information\Dedup\ChunkStore\{01BA1740-4874-4027-BC7F-74DD6B0DC52A}.ddp\COW\00100000

    Assuming the root cause is the same, has the issue been identified and a fix impending in DPM 2012 R2 as well?

    Friday, April 28, 2017 5:23 PM
  • HI,

    Yes, the same issue occurs in DPM 2012 R2 and is scheduled to be fixed in the next DPM 2012 R2 update rollup (UR13).


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, May 2, 2017 3:35 PM
    Moderator
  • Thanks for the update. In the meantime, is there any way to get a sense of what is actually being impacted by the missed files? Is an unoptimized backup a potential workaround?
    Wednesday, May 3, 2017 1:57 PM
  • HI,

    Yes, the same issue occurs in DPM 2012 R2 and is scheduled to be fixed in the next DPM 2012 R2 update rollup (UR13).

    Hi Mike,

    I see you have updated DPM 2016 fix to be in UR4 and not in UR3.

    Any idea of the approximate release date (weeks/months) on the DPM 2012 R2 UR13 and will it include the fix?

    Wednesday, May 3, 2017 3:23 PM
  • Hi,

    Generally speaking System Center products release updates on a quarterly basis.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, May 3, 2017 9:15 PM
    Moderator
  • AdamMT

    <snip>
    In the meantime, is there any way to get a sense of what is actually being impacted by the missed files
    >snip<

    Actually, these are false errors caused by a code defect that erroneously added folders to a fixup code path, but folders are not handled by that particular code path so we get these errors.  They can safely be ignored and your files are being protected.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by AdamMT Friday, May 5, 2017 1:33 PM
    Thursday, May 4, 2017 5:44 PM
    Moderator
  • Waiting quarterly for backup breaking fixes is unacceptable.  We have been without consistent stable backups Since October of last year due to the problems with the product and waiting for months for fixes that are on a "Schedule".  We have to babysit DPM daily due to problems with the software.
    Tuesday, May 9, 2017 3:35 PM
  • Waiting quarterly for backup breaking fixes is unacceptable.  We have been without consistent stable backups Since October of last year due to the problems with the product and waiting for months for fixes that are on a "Schedule".  We have to babysit DPM daily due to problems with the software.

    Right?!  I found this thread because I was searching for the same issue -- empty logs backing up deduped sources.  At least push a hotfix out for those of us who rely on (our bosses) seeing green checks in the DPM console.

    Also, question as to how DPM backs up deduped files at the volume level: is it rehydrating the files as it backs them up, or is the deduped volume backed up as-is (relying on the chunks stored in SysVolInfo)?  On the one hand, I like the idea that we would see the space savings on live and backup sources (without resorting to the terribly convoluted setup I've seen on technet to dedupe DPM storage with a bunch of small VHDXs stitched together with storage spaces).  On the other hand, I kind of like the idea that our backups would not be reliant on dedupe and could give me an entire file set if dedupe craps the bed (which it already did once already, majorly, under WS2016).

    Thursday, May 25, 2017 6:45 PM
  • NM - did some reading, and it's definitely backing up the volume as is, deduped.  So, it does need to get every chunk backed up.  Maybe it's trying to back up in the middle of an dedup optimization job?
    Thursday, May 25, 2017 7:09 PM
  • Update 13 has been released and seems to have resolved the issue for us:

    While synchronizing a deduped volume, alternate synchronizations raise an alert that synchronization of a few files failed, which is resolved for the subsequent synchronization.

    https://support.microsoft.com/en-us/help/4021873/update-rollup-13-for-system-center-2012-r2-data-protection-manager

    Thursday, June 22, 2017 2:43 PM