On Wed, 2004-09-29 at 08:55, Kostas Kalevras wrote:
> On Tue, 28 Sep 2004, Paul wrote:
>
> >
> > What i need is failover for accounting and session tracking.
> > Auth will be done using LDAP.
> >
> > Mirroring the DB is not possibe because accounting has alot of inserts,
> > that would need to have multi-master replication.
> >
> > I would like to use application data mirroring instead, having 2
> > databases and both servers writing(acct)to both but not fail unless
> > both databases are not accessible, reading (session) from local
> > only and failover to the other DB in case of failure only.
>
> For accounting replication your best choise is radrelay. For failover, just use
> a failover section in radiusd.conf
>
Radrelay is only for text file accounting, not SQL. (unless i'm wrong)
I would like to use sql instead, that why i want to write to both DB's.
How would you configure accounting to only fail when both entries,
sql1 and sql2, fail ?
> session{
> redundant{
> sql1
> sql2
> }
> [...]
> }
>
> authorize{
> [...]
> redundant{
> ldap1
> ldap2
> }
> }
>
> We have a similar setup working just fine in the Greek School Network (two
> radius servers, serving different regions but keeping full accounting).
>
> --
> Kostas Kalevras Network Operations Center
> [EMAIL PROTECTED] National Technical University of Athens, Greece
> Work Phone: +30 210 7721861
> 'Go back to the shadow' Gandalf
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
