If all looked well, I'd delete "-dry-run" and let it go. Finally, running multiple instances of rsync for different parts of your transfer could be a big help.
It's possible if you send the output to a file like this rsync -a /source /destination >/somewhere/rsync.out 2>/somewhere/rsync.err - the first > basically prints a file with all the stuff you would normally see, and the 2> refers to error messages.-exclude-from or something similar to exclude files you might not need will cut down the time, but it won't increase your transfer speed.-S to handle sparse files well - can't hurt if you don't have sparse files.
#JUMPY ULTIMATE BACKUP SD CARD PERMISSION UPDATE#
-W to copy files whole - always use this if you don't want it to compare differences never mind that the point of rsync is to compare differences and only update the changes.Also - I can't find any documentation for -no-compress. That's a much smaller average file size though. With -no-compress, I get 18 MBps, and without it I get 15 MBps. I synced to a different partition on the same internal SSD drive. my test was 13,000 files, total size 200MB, and using rsync 3.1.3. No -z - definitely don't use -z as in the OP.So, using rsync to copy to an empty directory? Here are some ways to speed it up: More here - that's a pretty dry read, but the cover picture is worth it.
There's probably an io bottleneck influencing the speed in the OP's case. First - the number of files in this case is going to be a major factor.
0 kommentar(er)
