HotTuna writes "I'm responsible for a closed, private network of Retail Stores connected to our corporate office (and to eachother) with IPSEC over DSL, and no access to the public internet. We have about 4GB of disaster recovery files that need to be replicated at each site, and updated monthly.
The challenge is that all the enterprise file replication tools out there seem to be client/server and not peer to peer. This crushes our bandwidth at the corporate office, and leaves hundreds of 7Mb DSL connections (at the stores) virtually idle.
I am dreaming of a tool which can 'seed' different parts of a file to different peers, and then have those peers exchange those parts, rapidly replicating the file across the entire network.
Sounds like Bit Torrent you say? Sure, except I would need to 'push' the files out, and not rely on users to click a torrent file at each site. I could imagine a homebrew tracker, with uTorrent and an RSS feed at each site, but that sounds a little too ghetto to fly by the CIO...
What does Slashdot think? Is Bit Torrent an appropriate protocol for file distribution in the enterprise? If not, why not? If so, how would you implement it?"
This discussion was created for logged-in users only, but now has been archived.
No new comments can be posted.
Sortof... The IPSEC tunnel goes back to a Data center with a crazy fat pipe, so the round trip from store to store does not travel over our HQ connection. our HQ is just another peer.
Re: (Score:1)