Depending upon your view of cheap you could use the rsync capabilities built into something like a pair Netgear ReadyNAS, with something else to create a VPN connection between the two boxes. Simple, effective, and depending upon the type of drives used it can be cheap.
-----Original message----- > From:Shawn <sgro...@open2space.com <mailto:sgro...@open2space.com> > > Sent: Friday 27th September 2013 15:57 > To: CLUG General <clug-talk@clug.ca <mailto:clug-talk@clug.ca> > > Subject: Re: [clug-talk] offsite backups > > > I'd be curious to hear as well. But maybe a private message with > details would be better suited. > > As for Andrew's comments, this is more or less what I was picturing. > Except it'd be a relatively cheap NAS from Memex, on some employee's > home connection (likely the owner) and set up to do rsync nightly. The > box is populated in the office to start with... Still, I like that the > more professional option is out there. > > Any other solutions for this sort of thing? > > Shawn > > On 13-09-27 03:17 PM, Gustin Johnson wrote: > > What company is this? I/we are looking are looking for co-lo > > (specifically for storage) options. > > > > > > On Fri, Sep 27, 2013 at 1:05 PM, Andrew Robinson > > <and...@boohahaonline.com <mailto:and...@boohahaonline.com> > > <mailto:and...@boohahaonline.com <mailto:and...@boohahaonline.com> >> wrote: > > > > __ > > > > Hi Shawn, > > > > For something of this size I've always found that the price of cloud > > storage to be insane. Amazon for instance would be about $380 a month for > > 4 TB. The more cost effective way of doing it is to host it on your own > > hardware in an offsite location. In terms of the initial seeding of the > > 4tb, the easiest/quickest way of doing it is to make a local copy of your > > data, ship that copy to the offsite location, and copy the data locally at > > that point. Otherwise you could be looking at several weeks to transfer > > that amount, as you would want to throttle your upload during business > > hours, instead of running full out 24 hours a day, and crippling your > > business internet. > > > > > > > > I suppose I should throw out there, that the company I work for offers > > co-located NAS storage in downtown Calgary, with a dedicated VPN link to > > your site, for exactly this type of scenario. Use whatever method you > > prefer for transferring the files over the VPN, there is no vendor lock in, > > the only limitation is that the space provided is for a typical 4 to 6 bay > > NAS. If you were thinking of building your own rack mount box than the > > co-lo prices would be more expensive. > > > > > > > > > > -----Original message----- > > > From:Shawn <sgro...@open2space.com <mailto:sgro...@open2space.com> > > <mailto:sgro...@open2space.com <mailto:sgro...@open2space.com> >> > > > Sent: Friday 27th September 2013 11:34 > > > To: CLUG General <clug-talk@clug.ca <mailto:clug-talk@clug.ca> > > <mailto:clug-talk@clug.ca <mailto:clug-talk@clug.ca> >> > > > Subject: [clug-talk] offsite backups > > > > > > > > > Hi all, > > > > > > I'm not sure if this is OT or not. But I'm looking options for > > doing an > > > offsite backup of 4+ TB of data. I don't know if a cloud solution > > would > > > be the best choice, or a dedicated virtual server somewhere, or > > if there > > > is a better choice. I'm not looking for the "cheapest" solution, but > > > for a reasonable solution for a business. > > > > > > I think this may be partly on topic for the list because I can > > see ways > > > to do this with a Linux box and a simple rsync script, but I'd > > like to > > > learn more about the professional solutions to this problem. > > > > > > The big issue is the initial transfer of 4+TB of data. > > > > > > Thanks for any input. > > > > > > Shawn > > > > > > _______________________________________________ > > > clug-talk mailing list > > > clug-talk@clug.ca <mailto:clug-talk@clug.ca> > > <mailto:clug-talk@clug.ca <mailto:clug-talk@clug.ca> > > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > <http://clug.ca/mailman/listinfo/clug-talk_clug.ca> > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php > > <http://clug.ca/ml_guidelines.php> ) > > > **Please remove these lines when replying > > > > > > > > > _______________________________________________ > > clug-talk mailing list > > clug-talk@clug.ca <mailto:clug-talk@clug.ca> <mailto:clug-talk@clug.ca > > <mailto:clug-talk@clug.ca> > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > <http://clug.ca/mailman/listinfo/clug-talk_clug.ca> > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php > > <http://clug.ca/ml_guidelines.php> ) > > **Please remove these lines when replying > > > > > > > > > > _______________________________________________ > > clug-talk mailing list > > clug-talk@clug.ca <mailto:clug-talk@clug.ca> > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > <http://clug.ca/mailman/listinfo/clug-talk_clug.ca> > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php > > <http://clug.ca/ml_guidelines.php> ) > > **Please remove these lines when replying > > > > > _______________________________________________ > clug-talk mailing list > clug-talk@clug.ca <mailto:clug-talk@clug.ca> > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > <http://clug.ca/mailman/listinfo/clug-talk_clug.ca> > Mailing List Guidelines (http://clug.ca/ml_guidelines.php > <http://clug.ca/ml_guidelines.php> ) > **Please remove these lines when replying >
_______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
