Thanks for the additional information. I assume that the statistics you provided were from 0.9.6?
Some things I notice, some recommendations, and some more questions:
- This backup you shared - was that a pretty normal 24-hour backup?
- I noticed about 38% of files are either new or modified - about 90,000 files in total. That’s a lot, does that normally occur on a daily basis?
- The total amount written to the repository was 49GB. That’s a fairly substantial amount of data - but as you noted, this is only about 2% of the total archive, and I wouldn’t expect it to take multiple hours.
- I have not observed big differences between the reported duration and the actual duration, but I am interested. Can you time your backup more precisely to measure the difference between actual backup duration and reported backup duration? You can measure this actual duration easily using the
time command like this:
% time restic -r /Volumes/SOURCE_A backup /Volumes/SOURCE_B. This will report real, user and system time for the execution of the backup.
- Can you share some statistics about your repository? (size of the repository in files and bytes? Number of snapshots?)
- Here’s a command-line you can use to get more information about WHERE restic is spending its time:
% restic -r /Volumes/SOURCE_A --verbose --verbose backup /Volumes/SOURCE_B | perl -pne 'print scalar(localtime()), " ";' | tee /tmp/my-bkup-output
This will create
/tmp/my-bkup-output with double-verbose output and a timestamp on every line. From there, you can filter out the least interesting lines to gain insight into where restic is spending its time.
% cat /tmp/my-bkup-output | grep -v -E "2019 unchanged|2019 new|2019 modified"
Hope this helps.