Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Concurrent backups of remote hosts #18

Closed
senji-rsbackup opened this issue Aug 31, 2014 · 4 comments
Closed

Concurrent backups of remote hosts #18

senji-rsbackup opened this issue Aug 31, 2014 · 4 comments
Milestone

Comments

@senji-rsbackup
Copy link

@senji-rsbackup senji-rsbackup commented Aug 31, 2014

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?

@ewxrjk
Copy link
Owner

@ewxrjk ewxrjk commented Sep 13, 2015

I've added issue #24 to request concurrent pruning. I'll probably attempt that before concurrent backup, as it's likely to be easier.

@ewxrjk ewxrjk added this to the 4.0 milestone Nov 29, 2015
@ewxrjk ewxrjk modified the milestones: 5.0, 4.0 Mar 25, 2017
@ewxrjk
Copy link
Owner

@ewxrjk ewxrjk commented Apr 14, 2017

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.

@ewxrjk ewxrjk modified the milestones: 5.0, 6.0 Jan 27, 2018
ewxrjk added a commit that referenced this issue Dec 29, 2018
ewxrjk added a commit that referenced this issue Dec 29, 2018
ewxrjk added a commit that referenced this issue Dec 29, 2018
ewxrjk added a commit that referenced this issue Dec 29, 2018
ewxrjk pushed a commit that referenced this issue Jan 14, 2019
#18
ewxrjk added a commit that referenced this issue Jan 20, 2019
ewxrjk added a commit that referenced this issue Jan 20, 2019
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
ewxrjk added a commit that referenced this issue Jan 20, 2019
ewxrjk added a commit that referenced this issue Jan 20, 2019
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
ewxrjk added a commit that referenced this issue Jan 20, 2019
ewxrjk added a commit that referenced this issue Jan 20, 2019
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
@ewxrjk
Copy link
Owner

@ewxrjk ewxrjk commented Jan 20, 2019

master now supports concurrent backups of distinct hosts to distinct devices - in other words, no concurrent use of any single resource.

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.

@ewxrjk
Copy link
Owner

@ewxrjk ewxrjk commented Mar 3, 2019

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.

@ewxrjk ewxrjk closed this Mar 3, 2019
ewxrjk added a commit that referenced this issue Sep 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants