This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 49%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The backup was successful with a warning. In the failed list, I get the following error message:
DATA FAILURE 0x80070013
DATA FAILURE 0x80070002
DATA FAILURE 0x80070003
It doesn't happen all the time. It was about once a week.
How can you solve it? Please tell me.
Make sure that MARS agent version on the servers are the latest version.
Another important points to check is, the privileges to access the files considered for the back up are good enough or not
Thank you for your advice.
The version is the latest.
A file that has no access privileges since has failed backup.
Another try is to see more details of the issue from the logs somewhere here: C:\Program Files\Microsoft Azure Recovery Services Agent\Temp\CBCmdlet0Curr.errlog
Check if VolumeShadowCopy backup to be excluded/included in the backup object
There is none.
There are a lot of errors like below.
2DD0 2980 04/01 19:00:08.960 79 CBClientCommon.cs(1265) NORMAL CBClientCommon::StartCBBackup - Policy name [a7619c7d-8989-4853-a212-b6ecf6bc71c1], Async [False], Force [True]
2DD0 2980 04/01 19:00:09.351 09 ApplicationSettings.cs(3759) NORMAL isDPMAServer:False, isDPMServerInstalled:False.
send us more details from the logs
These are the errors that occurred yesterday.
The same error remains on other days.
Log files are not showing the exact error messages you reported. Can you manually check the folders/files are presented in the computer which are reporting the backup error? Try to create any of those missing files/folders and see if the error resolves for the created objects in next backup. Also recommended to restart the backup agent before the next backup schedule kicks in
Try to create any of those missing files/folders and see if the error resolves for the created objects in next backup. Also recommended to restart the backup agent before the next backup schedule kicks in
The folder and file where the error occurred actually exist.
I asked the same question to the developers who introduced and implemented Azure to us, but they couldn't offer any countermeasures.