[Sunhelp] Opinions...

[Tim Conrad]

I think it'd probably have a lot to do with how often the data  on the server
changes...

If you have a LOT of data that changes very frequently, it's a more difficult
case :>

If your data doesn't change that freqently, it's a fairly simple case. Get a
few ftp servers, whatever you want them to be. There are various perl scripts
out there that mirror a ftp server. set up an ftp server as a 'primary' ftp
server, and have the other 2-3-4 mirror that main ftp server every hour or 30
minutes synchronizing the data.

There are also scripts that will automagically modify your dns records when a
server goes down. Server goes down, gets pulled out of the dns queue. Shouldn't
effect very many people. If dns was set up to round-robin, it would also help
with load balancing.

Although, this plan isn't flawless, either. Your data won't be synchronized to
the exact minute as with other solutions, but, the cost is very low.

Tim

Will Mc Donald wrote:

> This is completely OT (although not as much as Dreamcasts :)) but I wonder
> if anyone can spare the time to offer me some advice.
>
> What I'm trying to do is build a cheap-ish fail-over FTP cluster with a
> filesystem that's mirrored between the two machines over a dedicated 100
> Mbit network link. We've been looking at using High Availability Redhat as a
> failover FTP cluster. I can get the fail-over services working OK that's not
> the problem.
>
> The problem starts with trying to mirror at least one of the partitions over
> the network, I've looked into DRBD but I don't think it's developed enough
> yet. A few searches on google threw up references to Coda, Fault Freedom II
> and a rambling thread on slashdot discussing something along these lines.
>
> So, basically what I'd really like to know is does anyone here have any
> experiences/horror stories/advice to offer?
>
> TIA
>
> Will.
>
> _______________________________________________
> SunHELP maillist  -  SunHELP at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/sunhelp