DPM Backups Fail on File Server, (ID 2033 Details: The System Cannot Find the File Spedcified (0x80070002)

Question

I've found a few treads and posts related to this error, but none of the answers seem to work. I have DPM 2010 U7 server backing up my file server (Server 2008 R2). The backup of the D: Drive(which hosts all shares) is failing with the following error:
Affected area: D:\Occurred since: 4/23/2014 11:15:26 AMDescription: The replica of Volume D:\ on XXXXX.XXX.XX 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) DPM encountered an error while performing an operation for \\?\Volume{bb191e08-5d62-4a60-85f1-cdbd7598976b}\XXXX\XXXXX\XXXX\XXXXX\XXXXX\XXXXX\XXXXX\XXXXX\XXXXX on XXXXXX.XXXX.XXX (ID 2033 Details: The system cannot find the file specified (0x80070002))
I've ran SFC /SCANNOW on both servers, rebooted. Ran chckdsk /f on the D: on the file server, rebooted again. Still having the same issue. The BMR and System State backups run just fine, along with the backup of the C:
I am getting the following error on the file server for volsnap.
The shadow copies of volume D: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
Which caused me to try moving the shadow copy storage to the C:, but then it just fails with the following error. Which makes since as the C drive is 136GB, while the D drive is 27TB. 
The shadow copies of volume D: were aborted because the shadow copy storage failed to grow.
Lastly I deleted the entire replica and recreated the protection, with no luck.  I tried to just slowly create the replica by adding one small parts at a time, currently its failing while trying to backup ~300GB. 
I've checked the VSS Writiers on the file server, everything looks correct. Here is the print out.
P:\>VSSadmin List Shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
   For volume: (\\?\Volume{3c066165-11a2-11e3-ae8a-806e6f6e6963}\)\\?\Volume{3c0
66165-11a2-11e3-ae8a-806e6f6e6963}\
   Shadow Copy Storage volume: (\\?\Volume{3c066165-11a2-11e3-ae8a-806e6f6e6963}
\)\\?\Volume{3c066165-11a2-11e3-ae8a-806e6f6e6963}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: 32 MB (32%)
Shadow Copy Storage association
   For volume: (D:)\\?\Volume{bb191e08-5d62-4a60-85f1-cdbd7598976b}\
   Shadow Copy Storage volume: (D:)\\?\Volume{bb191e08-5d62-4a60-85f1-cdbd759897
6b}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: UNBOUNDED (61488716%)
Shadow Copy Storage association
   For volume: (C:)\\?\Volume{3c066166-11a2-11e3-ae8a-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{3c066166-11a2-11e3-ae8a-806e6f6e69
63}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: 13.603 GB (10%)
P:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {57babf83-3fb0-41c0-b13a-0ec09543d852}
   State: [1] Stable
   Last error: No error
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {2d4295b0-a282-4cd7-97af-ea394b845330}
   State: [1] Stable
   Last error: No error
Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {41c4fd48-af83-4ba8-9ca5-79820c055131}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {9a832588-4172-4f3a-bf44-363e128dfd74}
   State: [1] Stable
   Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {9c184685-c43e-4a6b-9b34-e82020329b1a}
   State: [1] Stable
   Last error: No error
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {e6db54bb-552e-4d8f-b26b-45aa03829fda}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {2c326c9e-8727-4277-833a-ee2cb76b625e}
   State: [1] Stable
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {e17f6d25-c8ad-4663-8511-c0d6a3413fe3}
   State: [1] Stable
   Last error: No error

Answer 1

Hi,
It is strange that the issue still exists after recreating backup.
Please try again to clear all replica, and specifically, move the folder involved in this error to another location such as Drive C and see if issue still exists.
Meanwhile please test if Windows Server Backup works or not. 
If you have any feedback on our support, please send to [email protected]