On Mon, Apr 21, 2008 at 1:14 PM, Kenneth Loafman <
address@hidden> wrote:
AJ Weber wrote:
> That seems to help...it's getting along further now. Surprising that
> out of the 6 different "sets", that's the only one failing.
>
> RELATED: It ended-up coming back with a "Warning...incomplete backup set
> found...". This is very possible. That set could have failed
> 'en-route' at some previous time. Can I trust Duplicity to make things
> right now? Or what is my best course of action?
Just run 'duplicity cleanup <target>' to clean out the incomplete backup
sets. Duplicity will ignore an incomplete backup, so it does the right
thing if one is there.
...Ken
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk