NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Rsync backup --ignore-times option
Hi,
I'm upgrading from a Duo to a 312, and in the process of copying all of my data - about 700GB - from the Duo over to the 312. I'm using the rsync backup method, as I'm keeping the Duo in use until the file copy is complete - looks like that's gonna take a few days...
One issue I noticed was that at least on the first full backup, the rsync command Backup invokes uses the --ignore-times argument. This effectively causes every file to be rewritten on the destination, and the speed it can do so is constrained by how quickly the source can send deltas, which in practice are null for 99% of my files, but the Duo has to calculate them anyway at Sparc-speed (read: slow).
I completed a backup run for one of my shares, and noticed that after the bulk copy completed, there's still an rsync process running, and still with the --ignore-times argument, which in practice is causing the full backup to take twice as long as it should. I can see rsync building temp files that eventually have the same md5sum as the original file, so this seems wasteful.
So two questions I have here:
- Does --ignore-times get invoked with regular backups as well as full backups? Is there a way to tweak this?
- If the answer to above is no, can I safely kill the currently-running rsync and invoke my own without the --ignore-times option for a final file sync before retiring the Duo?
Thanks!
I'm upgrading from a Duo to a 312, and in the process of copying all of my data - about 700GB - from the Duo over to the 312. I'm using the rsync backup method, as I'm keeping the Duo in use until the file copy is complete - looks like that's gonna take a few days...
One issue I noticed was that at least on the first full backup, the rsync command Backup invokes uses the --ignore-times argument. This effectively causes every file to be rewritten on the destination, and the speed it can do so is constrained by how quickly the source can send deltas, which in practice are null for 99% of my files, but the Duo has to calculate them anyway at Sparc-speed (read: slow).
I completed a backup run for one of my shares, and noticed that after the bulk copy completed, there's still an rsync process running, and still with the --ignore-times argument, which in practice is causing the full backup to take twice as long as it should. I can see rsync building temp files that eventually have the same md5sum as the original file, so this seems wasteful.
So two questions I have here:
- Does --ignore-times get invoked with regular backups as well as full backups? Is there a way to tweak this?
- If the answer to above is no, can I safely kill the currently-running rsync and invoke my own without the --ignore-times option for a final file sync before retiring the Duo?
Thanks!
3 Replies
- --ignore-times is not used on the incremental backups. The fastest approach is to use NFS, then edit the backup to use rsync and rerun it.
I'm not sure why you have a second rsync process running. - I actually have three rsync processes running right now; it appears that they're child processes of the primary rsync. No idea why rsync is spawning children though.
root@readynas312-1:~# ps aux --forest
...
root 2418 0.0 0.0 51420 1744 ? Ssl Sep11 0:01 /frontview/bin/fvbackup-q
root 10227 0.0 0.0 4176 576 ? S Sep13 0:00 \_ sh -c /frontview/bin/fvbackup -e 5
root 10228 0.0 0.1 92624 3744 ? S Sep13 0:00 \_ /frontview/bin/fvbackup -e 5
root 30682 0.0 0.0 4176 576 ? S 10:09 0:00 \_ sh -c RSYNC_PASSWORD=XXXXXXXXXXXXX nice -n 10 rsync -v -8 --recursive --links --times --devices --specials --one-file-system --ignore-times --owner --group --no-acls --no-perms root@192.168.1.128::Video
root 30691 5.0 0.4 35592 8824 ? SN 10:09 26:03 \_ rsync -v -8 --recursive --links --times --devices --specials --one-file-system --ignore-times --owner --group --no-acls --no-perms root@192.168.1.128::Video /data/Video
root 30759 5.5 0.1 35108 3748 ? SN 10:09 28:19 \_ rsync -v -8 --recursive --links --times --devices --specials --one-file-system --ignore-times --owner --group --no-acls --no-perms root@192.168.1.128::Video /data/Video - OK, turns out that's normal behavior for rsync: http://serverfault.com/questions/547165/why-does-rsync-spawn-multiple-processes-for-me
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
