duplicity-team team mailing list archive

[Kenneth Loafman <question658653@xxxxxxxxxxxxxxxxxxxxx>]

Question #658653 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/658653

Kenneth Loafman proposed the following answer:
A couple of answers:

No, the sigtar and manifest files are not split yet.

Version 0.7.03, 05/11/2015, was the first release with the --file-changed
option, so backing off to 0.7.02 should solve your problem.


On Thu, Sep 28, 2017 at 6:38 AM, Sivanath <
question658653@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Question #658653 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/658653
>
> Sivanath posted a new comment:
> Edso and Ken,
>
> Yes. This is my issues - once after creating large manifest file (lot of
> new, changed and deleted entries in it), the immediate next backup
> process was stopped due to memory allocation problem or simply skip with
> "killed" text. Please help me to  solve this issue. And Is there any
> option skip write these logs? Great Thanks for your help.
>
> --
> You received this question notification because your team duplicity-team
> is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help   : https://help.launchpad.net/ListHelp
>

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.