Hello Chris -
On Monday 19 March 2001 13:10, Chris M wrote:
> >> The only problem I forsee is, how do I make the SessionDatabase
> >> high-availability? In other words, is there a way to replicate
> >> the DB INSERTs and DELETEs so that auth or acct radiator
> >> processes talking to MySQL can have entries simultaneously
> >> made in SessionDatabases on two different machines? Since
> >> MySQL doesn't have any replication features built in, how do
> >> people accomplish this syncing?
> >
> > The simplest thing to do is just use a single SQL host, but use a
> > high-availability multi-processor machine with hot-swap RAID disks. This
> > is usually *much* easier to do than trying to replicate databases.
> >
> > hth
> >
> > Hugh
>
> I certainly agree and do this, however, there is always going to be the
> need to reboot the machine. Linux and other Unices still require reboots
> once a month.
>
I'll leave this argument to others.
> I just noticed that MySQL 3.23 has some kind of replication feature in it
> now, anyone used this that can give this a review?
>
One other approach is to use the new features in Radiator 2.18 to put a load
balancing proxy(s) in front of your production Radiator hosts, and configure
the proxy(s) with caching and accounting failover to a flat file. You can
then have the proxies run independently for the short periods of time that
your database is unavailable.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
