Re: S3 Backup using 2.6.1b2

2009-01-13 Thread Matt Burkhardt
On Mon, 2009-01-12 at 12:52 -0500, Dustin J. Mitchell wrote: On Mon, Jan 12, 2009 at 12:23 PM, Graham Wooden gra...@g-rock.net wrote: Also keep in mind the TCP sliding window when going over the Internet. You can have a fat pipe (on both ends), but the increased hop count and the TCP

Re: S3 Backup using 2.6.1b2

2009-01-12 Thread Dustin J. Mitchell
Sorry for the delay here. On Thu, Jan 8, 2009 at 11:32 AM, Matt Burkhardt m...@imparisystems.com wrote: I'm not too sure what's going on - it takes about 10 days to run the backup. Here's the results from the run that started on 12/27 and the results from amstatus on the backup that started

Re: S3 Backup using 2.6.1b2

2009-01-12 Thread Dustin J. Mitchell
On Mon, Jan 12, 2009 at 12:23 PM, Graham Wooden gra...@g-rock.net wrote: Also keep in mind the TCP sliding window when going over the Internet. You can have a fat pipe (on both ends), but the increased hop count and the TCP overhead you will only get a percentage of your pipe. In my

S3 Backup using 2.6.1b2

2009-01-08 Thread Matt Burkhardt
I'm not too sure what's going on - it takes about 10 days to run the backup. Here's the results from the run that started on 12/27 and the results from amstatus on the backup that started running yesterday. I checked S3, and it used up a little over 5000 tapes. Is there a time / amount limit?