Processing files which are not in backup sources

[JonMikelV]

@mnaiman

I think is that it reads files which is not supposed, because they are not in backup set.

Second is, that reading some system files (again not in backup set) are causing UnauthorizedAccessExceptions.

Thanks for reporting what you are seeing - and entering the GitHub issue!

I’m using 2.0.3.9 and not running into this issue, is it possible you’ve got a symlink or something in one of your included folders that points to your drive root?

@JensK

How can I safely rollback to 2.0.3.5?

This How-To topic should cover downgrading:

Downgrading / reverting to a lower version

WARNING! Due to changes in database versions it is not possible (well, very hands-on) to downgrade ACROSS these versions (as of 2018-10-28): 2.0.1.7 (using version 3 - 0 & 2 usage in preview releases only) 2.0.1.18 (move to version 4) 2.0.3.4 (move to version 5) 2.0.3.12 (move to version 6 - see Release: 2.0.3.12 (canary) 2018-10-23) 2.0.4.13 (unconfined move to version 7 - see *broken* Release: 2.0.4.13 (canary) 2019-01-29) 2.0.4.23 from 2.0.4.13 or newer (2.0.4.23 beta is a notification upd…

@JensK

Can the data that should not be backed up be deleted from the backup set?

Yes, but there are some things you should be aware of such as unless you adjust other settings it’s likely a large compacting will happen (meaning lots of downloads, re-compress, uploads) so if you’re on a bandwidth limited connection or provider you may not want to do that.

Also, if you have a retention policy in place that might (depending on settings) automatically take care of the cleanup once the wrongly included files are no longer being included.

I’m curious, can you share some of what paths were included unexpectedly with 2.0.3.8 / 2.0.3.9 but NOT with 2.0.3.5? It’s possible some default exclude code got screwed up at some point so identifying that would be good.