mirror of
https://github.com/borgbackup/borg.git
synced 2025-02-22 22:22:27 +00:00
Merge pull request #705 from manwegit/feature/docs-bwlimit
Faq: how to limit bandwidth
This commit is contained in:
commit
fbc4172c73
1 changed files with 26 additions and 0 deletions
26
docs/faq.rst
26
docs/faq.rst
|
@ -264,6 +264,32 @@ Since only the files cache is used in the display of files status,
|
|||
those files are reported as being added when, really, chunks are
|
||||
already used.
|
||||
|
||||
|
||||
Is there a way to limit bandwidth with |project_name|?
|
||||
------------------------------------------------------
|
||||
|
||||
There is no command line option to limit bandwidth with |project_name|, but
|
||||
bandwidth limiting can be accomplished with pipeviewer_:
|
||||
|
||||
Create a wrapper script: /usr/local/bin/pv-wrapper ::
|
||||
|
||||
#!/bin/bash
|
||||
## -q, --quiet do not output any transfer information at all
|
||||
## -L, --rate-limit RATE limit transfer to RATE bytes per second
|
||||
export RATE=307200
|
||||
pv -q -L $RATE | "$@"
|
||||
|
||||
Add BORG_RSH environment variable to use pipeviewer wrapper script with ssh. ::
|
||||
|
||||
export BORG_RSH='/usr/local/bin/pv-wrapper.sh ssh'
|
||||
|
||||
Now |project_name| will be bandwidth limited. Nice thing about pv is that you can change rate-limit on the fly: ::
|
||||
|
||||
pv -R $(pidof pv) -L 102400
|
||||
|
||||
.. _pipeviewer: http://www.ivarch.com/programs/pv.shtml
|
||||
|
||||
|
||||
Why was Borg forked from Attic?
|
||||
-------------------------------
|
||||
|
||||
|
|
Loading…
Reference in a new issue