I needed to back up some of my NAS over the WAN to another (friends) NAS (3/4TB-total). A lot of expensive hi-def music files, mostly very large. He backs up to mine, vice versa for disaster recovery. There were two issues: 1) sucking up all my UL bandwidth, only 5mbit in this case, 2) having the option to do a "delayed" kill of the rsync when it *finished* the current file rather than an immediate stop so as not to waste the bandwidth already used to move a portion of a large file. I implemented both with signals. A signal toggles the enable/disable of the --bwlimit=XXX param so you can do a simple throttle back or run wide open. The second signal is a delayed quit - when current file is finished. This seemed to work pretty well. During the day when I needed the BW for work, etc. I'd throttle it, then let it run wide open at night. This could be expanded with a BW list, so instead of a simple toggle, the next BW setting in the list could be used, round-robin. The delayed quit was nice if new content was added that I felt I wanted backed up first. Quit (delayed), then restart, easily scripted. Let me know if there is any interest in putting this in the code base and I'll create some diffs for review. Cheers, Frank On 4/3/14, 10:47 AM, Marian Marinov
wrote:
On 04/03/2014 03:35 PM, Christoph Biedl wrote: --
Frank Terhaar-Yonkers W4FTY Cisco Systems, Inc. 7025 Kit Creek Road PO Box 14987 Research Triangle Park, North Carolina 27709 f...@cisco.com voice(919)392-2101
|
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html