Best practices for redundant servers

[Stieven.Struyf at komatsu.eu]

I use a very simple system to get redundancy. I have 2 seperate radius 
servers. If i do a change i need to do it on both(biggest disadvantage).
In all my access points or other applications i can enter 2 radius 
servers. When the first doesn't answer it autom. authenticates to the 
second.

This has the advantage that i add another config to one of them for test 
systems, or to test some parameters without the change being synced to the 
other one.


Stieven Struyf
M.I.S. Division - System Operations 
Komatsu Europe International NV
Mechelsesteenweg 586
B-1800 Vilvoorde
Stieven.Struyf at komatsu.eu
Tel. +32 (0)2 2552551

freeradius-users-bounces+stieven.struyf=komatsu.eu at lists.freeradius.org 
wrote on 01/19/2007 05:42:02 AM:

> Dennis Skinner wrote:
>  > For serious billable accounting you probably want to write to files 
and
> > then import them into the db (there is a module to help with this).
> > Radius will happily skip queries that take too long or if there are 
not
> > enough mysql connections available on the accounting side.
> > 
> 
> I remember reading about 'radsqlrelay' that does essentially this. It is
> also mentioned once in radiusd.conf but subsequent searching has brought
> up nothing worthwhile.
> 
> Does anyone remember where there is doccumentation on this?
> 
> regards
> Graham Beneke
> - 
> List info/subscribe/unsubscribe? See 
http://www.freeradius.org/list/users.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20070119/52853e3f/attachment.html>