Hi Sorry to be posting a reply to my own email...
On Thu 05-Nov-2015 at 10:27:20AM +0000, Chris Croome wrote: > > I'm using s3ql to backup several servers and roughly every other night > one of the backup fails during the rsync with: > > rsync: write failed on "/example.file.txt": Transport endpoint is not > connected (107) I have just looked at the size of the file in question, a 240MB uncompressed plain text .sql dump, and this thread: - https://bitbucket.org/nikratio/s3ql/issues/61/10-maint-s3ql-crashes-when-backing-up I have been using the default number of threads (2?) and default compression, I'll change the number of threads to 1 (the virtual server running the backup has 512MB of RAM) but I'm unsure what I can do regarding the compression algorithm -- it can't be changed for an existing bucket can it? All the best Chris -- Webarchitects Co-operative http://webarchitects.coop/ +44 114 276 9709 @webarchcoop -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
