Merge lp:~harningt/duplicity/multibackend-mirror into lp:~duplicity-team/duplicity/0.7-series
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 1191 | ||||
Proposed branch: | lp:~harningt/duplicity/multibackend-mirror | ||||
Merge into: | lp:~duplicity-team/duplicity/0.7-series | ||||
Diff against target: |
293 lines (+174/-17) 2 files modified
bin/duplicity.1 (+55/-7) duplicity/backends/multibackend.py (+119/-10) |
||||
To merge this branch: | bzr merge lp:~harningt/duplicity/multibackend-mirror | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
edso | Approve | ||
Review via email: mp+286090@code.launchpad.net |
Description of the change
This changeset addresses multibackend handling to permit a mirroring option in addition to its "stripe" mode to make it a redundancy tool vs space-expansion tool. To do this without changing the configuration too much, I used the query string that would generally go unused for files to specify behavior that applies to all items inside the configuration file.
Testing would include testing that multibackend behaves exactly as it did before the change when no parameters are introduced and testing each of the (stripe / mirror) x (continue / abort) options.
Locally tested on 2 machine since around July 2015 were the mode=mirror onfail=abort modes to replace some shell-scripts I used to run after backup to synchronize a local backup with many backends.
looks good to me.. ede