Comment 64 for bug 385495

Revision history for this message
Arthur Andersen (leocgit) wrote :

I am having a directory of 400GB that is to be backupped by duplicity incrementally & encrypted to AWS S3. The sigtar file is almost 10GB in size, causing the backup to fail with `Broken pipe` (I suspect due to network connection loss, timeouts or limitations).

As of now I cannot split the backup into smaller chunks. Is there a work-around that I could use until duplicity splits sigtar files aswell?