implement remote-ratelimit #45
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#45
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adding support for borgs
--remote-ratelimit
parameter would be perfect.Regular backups should not disrupt normal operations by using all bandwidth. Using a ratelimit would be the way to go.
Imported from Taiga issue 44 (done). Created on 2017-11-01T15:44:38+0000 by Benjamin Häublein.
Just released borgmatic with support for a "remote_rate_limit" option in the "storage" section of config. Let me know how it works out for you.
Comment on 2017-11-03T05:40:14+0000 by Dan Helfman.
I get the following error when using the
remote_rate_limit
option:Comment on 2017-11-04T09:54:40+0000 by Benjamin Häublein.
Huh, that configuration option totally works here. (Just confirmed again.) Would you mind pasting your borgmatic configuration file? Please feel free to obscure any sensitive information (passphrases, hostnames, etc).
Comment on 2017-11-04T18:23:47+0000 by Dan Helfman.
Also, please double check that you're using the new version of borgmatic that contains this change! It's borgmatic 1.1.10 in particular. You can run
pip3 show borgmatic
to see that version number.Comment on 2017-11-04T18:24:59+0000 by Dan Helfman.
Shame on me. I only upgraded using pip. Even checked the new versions code on my machine. Totally forgot about python3..
Thanks. Works perfectly.
Comment on 2017-11-05T13:09:54+0000 by Benjamin Häublein.
Glad to hear it's working!
Comment on 2017-11-05T17:46:40+0000 by Dan Helfman.