![]() Adding -no-checksum doesn't alter things. The rsync tool should also work, but never tested that in a scenario like this one. I suspect this is caused by rsync checksumming the target files in the link-dest directory. In particular I want to preserve ownership, trustees, timestamps. There is heavy network traffic to/from the NAS and things go very slowly even though almost no data is actually transferred from source to target. But when I do my snapshot backup: rsync -a -link-dest=/mnt/nas/backup/yesterday /home/stuff/ /mnt/nas/backup/today However, through my actual verification, the file cannot successfully configure cwRsync, so it is recommended to configure it manually. Either dont give the -t flag (which is coming in via -a), or add -no-times after that on the command line. (when only a few files have changed since yesterday) because in this case rsync uses only its quick timestamp+size check to compare files. You are specifying (via the -a flag) that you want timestamps to be preserved on all files/directories, so its reporting that those changes will happen. The slowdown does not happen when doing the simple: rsync -a /home/stuff/ /mnt/nas/backup/yesterday ![]() ![]() The functionality is ideal, but it's unreasonably slow for the most common scenario: daily backup of a file hierarchy (~100GB, ~2000 directories) in which only a very few files have changed. I'm using rsync (version 3.0.9) to do snapshot-style incremental backup from local disk to a LAN-attached NAS that's mounted using cifs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |