Nick Holland wrote:
knitti wrote:
On 8/7/06, Jens Mayer <[EMAIL PROTECTED]> wrote:
While the networking part can be handled by carp, I'm collecting
ideas on how
to keep the local file systems in synch - especially for ftp users
and the
mailinglist archives. The synchronization will be done via a
dedicated cross
coonect cable directly between the boxes.
while I would do it with rsync (I know, depends on what you want to do),
I don't see any reason why ccd'ing two large nfs-exposed files shouldn't
work. But I think this would be more ugly and complicated than rsyncing
every x minutes...
Simplicity is your friend.
rsync is simple, easy to understand, and easy to recover.
mirroring over NFS is not simple. My money would be that you would
spend less time up and lose more data than a single, completely
non-redundant workstation (yes, no rsync, but with a good backup plan,
which you need anyway)...all in the name of "high redundancy".
No, I can't prove it, but I much prefer the simple solution which has
simple and understood problems, than the system which is never supposed
to break...and will anyway, in ways you never imagined, and may not be
able to figure out. Experience tends to suggest I'm right on that...
Nick.
Seconded, we buy a lot of expensive proprietary gear and ware here. No
one truly understands most of it, vendors wont tell us about it. It is
never supposed to break and when it does it is expensive to get fixed.
Home grown is great if it is dead simple/straight forward/elegant. If
you are going to go make a hairball you may as well buy one. That way
you can get to the pain quicker and it will take less time.
