Is there any way of using the disable-filetime-check instead of for an entire backup set but for a particular file or file(s) in the set?
The operating system keeps track of the last time a file was written. Using this information, Duplicati can quickly determine if the file has been modified. If some application deliberately modifies this information, Duplicati won’t work correctly unless this flag is set.
I don’t think you can do this per-file, but you can do it for a backup of all the files needing it.
Basically, if you want some files one way and some the other, how about two backup jobs?
Different backup jobs is ok to a point, but you need to then remember to exclude the files in one job, add them to another and then run both. Restoring files then needs to 2 jobs.
It would be nice for all of this to be combined to one job, with the exceptions for the time check set within that job.
I understand that some manual config will be required to add an exception to which files need to have the disable-filetime-check added but it feels like an easier solution that multiple backup or restore jobs?
It’s not easier because it’s not there. Would you like this to be a feature request?
There are more features than can be done, but maybe someone else wants this.
Yeah I think a feature request would be good. I think it would be a great addition and in my case, and a few others after looking over the forum, it would definitely help speed up my backups as I only need the disable time check for a couple of files out of loads of files in a set.
Changed topic from Support to Features category.
I think this makes sense. I know some applications do not set the timestamp by design (encrypted containers, etc).
In this case it would make sense to have a filter-like expression, something like --disable-filetime-check-include=*.iso.
Feel free to create an issue for this:
Yeah, thanks!
That’s exactly it, if certain files are done like this by design, it would be nice to disable the time check just for those and not the whole set.
This way, they will still get backed up/checked on every run, but the backup will be a lot quicker as everything else doesn’t need to be checked again.
I’ve created the issue as requested, thanks for considering this.
but as it turns out, there was this one a few days earlier. I don’t know if it was forum-inspired.
1 Like
Oh yes, sorry I didn’t see that.
Hopeful the feature will be considered as it seems like a few people may benefit from it?