As I tune my new backup tasks, mainly to eliminate unimportant errors, I start to think that this would be much easier if there were a general application setting like "global exclusions". What do others think? A useful feature, or some basic misunderstanding by me?
Here are some examples of errors, related to directories and files that I am 99.9% certain I would never need from a file backup. Sure, I have them in my disk-image backups - much different beasts. But for my file backups, Windows and apps are gonna do what they're gonna do on a pc, and I would never retrieve dirs/files like these from backups:
- ERR date/time An error occurred while copying "C:\Users\...\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData\57C8EDB95DF3F0AD4EE2DC2B8CFD4157" to "\\backup-path\Users\...\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData\57C8EDB95DF3F0AD4EE2DC2B8CFD4157": Access is denied
- ERR date/time An error occurred while checking for mirror changes: (5) Access is denied: [\\backup-path\Users\...\AppData\Local\Mozilla\Firefox\Profiles\profile-ID\startupCache\scriptCache-child-current.bin]
I use jam-soft's TreeSize to find bloated directories. When I find them, I'd like to add them to a global exclusion list, and henceforth have much faster and smaller backups. Sure, drive space is relatively cheap these days. But bloat, to me, is exceptionally obnoxious - especially when I'm trying to protect and later find a meaningful file or configuration - and I don't need to slow my pc and network down to backup up endless bloat.
So that's my feature request and use case, and I'm happy to see any opinion or suggestion.
And once we have that, we can crowdsource anti-bloat exclusion lists, so we're not all fumbling to find these on our own : )