Discuss: In !153 restart may ignore missing volumes
Adding a separate Issue for a discussion from another MR !153 (comment 1693542956)
Restarts will only check and retry the last volume written to manifest only. This likely good enough if all volumes transferred in strict sequence. Especially as there is a validation by size after each transfer.
With async and concurrent transfers this flow is not sufficient, as e.g. the transfer of vol2 can fail after the transfer of vol7 was logged successful to the manifest. In this case duplicity recovers from vol7 not from vol2.
(for --concurrency
there are some countermeasures implemented)
I just want to log it here for visibility and to get an agreement if this behavior is "good enough" or if there are some fixes or advises required or may be I overrate this all.