4 ms·
Once you go unison you will never want to go back. I even run some ZFS without ECC memory, because if hardware goes bad and programmatically corrupts it isn't
by mindslight 10y ago
Once you go unison you will never want to go back.
I even run some ZFS without ECC memory, because if hardware goes bad and programmatically corrupts it isn't the end of the world.
- Annatar 10y agoWhat is "unison"?
- mindslight 10y agoBidirectional file synchronization. It makes any single replica not that important. Don't concentrate your resources into a single "invincible" box.
- Annatar 10y agoIs the synchronization synchronous or asynchronous? Is there a uniform resource identifier where I could read more about it? Or perhaps some book? Research paper?
- mindslight 10y agohttps://www.cis.upenn.edu/~bcpierce/unison/ https://www.cis.upenn.edu/~bcpierce/unison/ It synchronizes directory trees on arbitrary filesystems, so I think the answer to your question would be "asynchronous". Most individuals don't have TBs of working set continually being updated and requiring a central authoritative copy. They have a small working set and a long-term archive they'd just never want to lose. Unison's model isn't perfect (eg having to create a star topology, lack of built-in inotify). But it's been around forever, is written in a sane language, and is rock solid.