On 06/06/2014 07:00 PM, Matthew Caron wrote: > Why not just use unison? Greetings,
I have been toying with a very similar idea. In my very limited personal testing, using unison worked rather well, but I wasn't able to scale with it. Doing a three-way sync didn't go well at all. I personally view the primary benefit of owncloud as a way to store data I care about that I *don't* necessarily want other cloud providers to know about (eg: syncing all of my phones contacts and data to my owncloud vs Google's cloud). Should I go away on a business trip and power knocks out my server while I am gone, I don't want to lose access to all of my files! (as has happened twice in the last year; once got the router stuck in a bad state and the second time power was out for more then 20 minutes so UPS did a shutdown.) This really sucks! I would love to host at least two other servers; one at my parents and one at my sisters. That would cover 3 different states with a radius of just over 500 miles. Not only would that give me a good fault tolerance but it would improve local LAN speeds for them as well! I have been trying to experiment with some distributed file systems. My experiment with OrangeFS did not go so well. I got a hold of one of their engineers at a conference and chatted about some of my issues and basically got the answer "Eek. Yeah, we don't do that." The best I could get was that the next revision might make it easier, but they don't replicate a shared file-system in a consistent enough manner. I started doing some research into Tahoe-LAFS, and there is some promise there, but see the other conversations on this list and on the owncloud forums for other peoples take on it. I will probably take a stab at it this summer, but there are some certain limitations with it combined with owncloud. It's not much hope, but it is the best hope I have at the moment. But my concern for multi-server support isn't just all personal either. I tried really hard to get it in at work but lost out because it failed almost all of the requirements for fault-tolerance/fail-over/DR site/ect because the best setup I could manage was a cron-job rsync to another server + heartbeat fail-over. Instead they are beta testing a proprietary product that does scale really well but has a terrible interface and a 1/4 of the feature sets of owncloud (though to be fair to them, their whole company is based on enterprise grade storage...the whole acting as a file share thing is more of a 'sure, why not?' after thought). Anyway...longer then I meant it to be, but thought I would chip in on unison plus some things I thought were relevant. :-) ~Stack~
signature.asc
Description: OpenPGP digital signature
_______________________________________________ User mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/user
