TW
TW
The default log output only includes the messages, but not: - the timestamp - the level (like DEBUG, INFO, WARNING, ERROR) But, as borg uses the `logging` module, this is...
Besides tweaking the logging, you could also: - snapshot the filesystem, so files don't change while borg reads them, or - exclude unimportant files that are expected to change or...
please check the faq, there are instructions about how to debug and resolve speed issues.
So, what status char (leftmost in log output) does it show for most files when using `borg create --list ...`?
So the files are all "M"(modified), "A"(added) (and a few "E"(error) due to permissions). That means that borg thinks they are modified and that is why you get bad performance....
That log is a mess because you mixed --progress and --list. For more clarity, just use --list without --progress.
And likely your smb server messes up ctime somehow. Maybe it works better with `--files-cache=mtime,size`. You need to run at least 1 complete (and slow) backup **before** you will see...
"U"(unchanged) is good and will give great performance.
Any news?
You said you see mostly "U". That should solve the speed problem. "U" means that borg does not read the files' content because it is unchanged. It then takes the...