Re: [Duplicity-talk] large upload "ETA stalled"?

[Ted Timmons]

Thanks. I'm using the B2 backend (backblaze) and am on the latest gzip (0.7.11).

Maybe I'll look into the b2 connector and compare it to s3.

On Thu, Jan 12, 2017 at 4:22 PM Cláudio Gil <address@hidden> wrote:

Hi,

I've used this chance to explore the source code and it's seems that reporting progress is the "responsibility" of the backend. The S3 or Dropbox backends, for example, report progress but some (most?) don't. You haven't mentioned the version of duplicity you are using but it should apply.

In any case, the progress tracker uses a 5s window to determine if the upload is stalled. So, if the backend does not report progress you will always get "stalled". For S3 you can "stall" if the upload rate is bellow 25KB/s and for Dropbox you may "stall" if the upload rate is bellow 3MB/s, I believe.

Cheers,

Cláudio

2017-01-12 1:01 GMT+00:00 Ted Timmons via Duplicity-talk <address@hidden>:

I'm doing a big backup. It'll take days/weeks to complete. With --progress turned on, I see this:

0.0KB 15:00:22 [0.0B/s] [>                                        ] 0% ETA Stalled!

I know it isn't stalled because I can see the volume size on the remote end getting bigger. Is this to be expected?

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk