Concurrent backups of remote hosts #18
Comments
|
I've added issue #24 to request concurrent pruning. I'll probably attempt that before concurrent backup, as it's likely to be easier. |
|
https://github.com/ewxrjk/rsbackup/wiki/Concurrency is the design. It's been implemented for pruning but not for backups, which will be a substantial upheaval. |
The current logic is that no resource should be used concurrently with itself - so at present slow hosts being backed up to a fast device will still be serialized. re #18
The current logic is that no resource should be used concurrently with itself - so at present slow hosts being backed up to a fast device will still be serialized. re #18
The current logic is that no resource should be used concurrently with itself - so at present slow hosts being backed up to a fast device will still be serialized. re #18
|
Concurrent use of devices and/or hosts could potentially be added, if that's desirable. The former might produce poor locality of reference on backup devices? #17 would need to be addressed before supporting concurrent use of volumes. |
|
I'm going to reject idea of concurrency 'within' devices and have created #58 for concurrency with hosts, meaning that this issue is now closed. |
When backing up remote hosts it seems that rsbackup is rarely if ever I/O bound on the target device; would it be possible to have a configuration option to run backups on multiple hosts at once?
The text was updated successfully, but these errors were encountered: