I am looking for a way to limit the times during which an RSYNC backup between two ReadyNAS units can run (e.g. a NAS to NAS backup over VPN that can kill bandwidth).
I understand how the ReadyNAS scheduling window allows a job to start anytime during the start and end time you specify, but that really isn't always that helpful. If you have multiple jobs that queue up and you are still within a window than the next job can still start and that's fine. However, if you added a nice little checkbox to the settings panel for the backup job (feature request!) that could flag whether a job would either a) complete no matter how long it takes (as it does now) or b) stop the backup until the next scheduled backup window occurs, it would make life SO MUCH easier. When running RSYNC jobs for a LOT of data, at least initially, it kills bandwidth. The ability to limit the window that a job can run would be very valuable. If I can run a backup between 1-5am for as many days as necessary, eventually RSYNC will build a full backup and eventually be able to backup incremental changes without an issue thereafter. As it stands now, if I start that job and let it go, it will kill the pipe. I need to stop it manually after people start complaining or remember to catch it beforehand. If anyone has a workaround, please let me know. I have tried to do a Windows copy of the data to the NAS so most of it is there and then run an RSYNC but RSYNC doesn't like that. I think my only other options are to keep stopping the job or move my offsite NAS temporarily onsite and let them SYNC there and then take the offsite NAS back offsite and SYNC from that point forward. Suggestions?
Re: Backup Scheduling and Limiting Runtime / Rsync
There is a --bwlimit=RATE option - it'd be nice if there was a way to set it as an advanced parameter in the backup job(s). A throttled backup would always run slower, but that might be better than killing the job when the time expires.
