Hello,
my backup has a warning because of one file in the Firefox profile. I have 2 questions.
Why is ParsedResult: Error in my report although there is only a warning. I use www.duplicati-monitoring.com and I always get thre reports marked as error. I think it should only be Warning.
2 Why do I get the error with this file? Duplicati runs as service and uses snapshots. So all files should be accessible.
I use Duplicati - 2.0.2.13_canary_2017-11-22 on Windows 10
Generally the “storing empty metadata” and “Failed to process path” seem to come together and seem to be caused by a permissions issue rather than an in-use situation. So in this case I doubt snapshots has anything to do with the problem.
My first guess is it’s related to these possibly being temp files that Firefox is locking down permissions wise for general system security reasons.
I’m running that as well (64 bit on Windows 10) so I set up a test backup of just my Mozilla folders.
With Firefox running and no snapshot settings or --snapshot-policy set to Off I get " Failed to process path" errors, but no “Storing empty metadata” messages.
With --snapshot-policy set to Required, On, or Auto I get no errors at all. If you verify your --snapshot-policy is Required, On, or Auto then I’m pretty sure it’s a permissions issue.
Note that it looks like the folder structure you’re using isn’t the normal Windows one I’m used to where Firefox is a subfolder of a Mozilla folder. Are you using a custom version of FF in some way?
It appears that the snapshot is in place (the \?\GLOBALROOT\... stuff), but still permission is denied.
I don’t know why this happens, but I think it is a general VSS issue. Googling the problem did not reveal anything, but maybe I hit the wrong keywords…
I guess it is a matter of preference when things are considered a warning and when it should be considered an error. When you have any files that caused errors, as indicated with FilesWithError: 1, then the status is reported as Error. But i agree that it does not make sense since the message is logged as a warning. We should go either one or the other.
Is there any progress with the error result? I have now several backups in my duplicati-monitoring.com and its nearly unusable, because most of them result in an error, because of one or two unimportant files that could not be backuped.
What exactly is your --snapshot-policy set to? If it’s set to “Auto” then it may be failing without you noticing. You can set it to “On” to trigger a more noticable warning when the snapshot fails.
Also, I would not bother backing up OST files. That’s an offline cache of your email data. If the file is lost or damaged the data will be re-downloaded from the email server automatically.
Yeah I have seen comments about that OST files are not worth backing up. But duplicati is about keeping your own backup in your own system. So if I have trusted the email providers and other cloud providers I would not have bothered to backup anything.
If Duplicati is successful in making a snapshot, then Outlook being open should not matter. I suspect it may still be failing to create a snapshot. Can you try setting --snapshot-policy to “Required” and running another backup? This will make it more obvious if the snapshot fails.
Is it possible you are changing this at the global settings level, but the job has a different snapshot policy set? (You can set most/all options at the global level and at the job level. If undefined at the job level, it will use the global level settings.)
Could be, but then it would do that randomly. Cause when I first set up the job I did not use snapshot policy, and the I got the corresponding error to that. (Can not access file because locked by other process etc)
I have not touched the job level settings at any time. (Other than those that the “wizard” shows predefined)
Try this - go to the Duplicati web UI, click your backup job, and click Export.
On the next screen click “As Command-line” and uncheck the “Export passwords” box.
Click Export, then copy and paste the results here (sanitized of any sensitive info). Alternatively, instead of pasting here, you can look through the text for --snapshot-policy and confirm the setting.
I exported it and there was nothing about --snapshot-policy.
Just for fun, I created a new backup test and set the snapshot-policy in the job settings, but I got the same error.
I have also confirmed that the service is run as a local system account.
When I first set up the initial backup (without VSS) I saw that many files were not backuped. But when I enabled VSS there was only the OST file. Maybe it could be the size or the file name? (Just throwing out something) Since my OST file contains a dash (-) and also the file in question for the thread starter also contains a dash.