OT: Sending 65GBs over the interwebs

[Mark Suszko]

Why not use Extreme Reach?

[Jeremy Garchow]

Client doesn’t have a destination code. 🙂

[Jeff Kirkland]

The Bittorent solution might take a little more to set up but once that’s done a client shouldn’t have to do more than click on a link to launch the torrent app and then select where to save the file. Most people will have an I.T. guy somewhere that can do the initial install for them.

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeremy Garchow]

Thanks, Jeff, and everyone, for your insight.

I got the first file up via ftp in about 10 hours. The next file is still big, but smaller.

I would have like to do the torrent option, but it was just too ‘difficult’ (not really, but you know what I mean).

This is only a one or three off transfer at the most. If I had to do this all the time, I would definitely explore a torrent.

[Mark Suszko]

I’m curious about BitTorrent for solving these large file transfer problems, but, my clients and superiors would be put off by it’s “seedy” reputation, and security concerns. What’s a good background resource on Torrenting for answering the concerns of “legitimate” users?

[Phillip Hollweg]

So far as uploading goes, I have read FTP over TCP/IP is not the fastest use of bandwidth. Google Chrome uses a faster Google network protocol to Google sites and services. Google Apps for Work Unlimited is $10/user/m, and can be shared with anyone. I have not tested side by side, but it might give a faster upload speed over the same pipe as FTP, and the unlimited sharing is inexpensive for a small number of employees.

(We are trying to find a way to upload 24TB of data to Google apps. Upgrading our bandwidth for a month seems to be the only option. So, I have been looking into this recently…)

[Walter Soyka]

BitTorrent Sync uses the same transport technology as BitTorrent, but not the same seedy (get it?) tracker system. The link I shared above is probably the best resource for describing the legitimate use.

Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

[Jerome Raim]

I’d second Google Drive – very fast and with a file size limit of 5TB.

Alternatively/additionally, I’ve occasionally used a tool to split a file into multiple xxMB chunks and asked the recipient to concatenate on their end (something like this). This was the perfect solution for unreliable FTPs that might lose a connection on anything larger than 500MB. To play it safe, I would provide MD5 checksums for everything as well.

Jerome Raim
Post-Production
JeromeRaim.com