Re: Best practices for redundant servers

--===============0961500739==
Content-Type: multipart/signed; boundary="nextPart2309267.afQ3TzV83o";
protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2309267.afQ3TzV83o
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Mon 06 Nov 2006 19:38, Aaron Paetznick wrote:
> Thanks, this was helpful. I would rather not use LVS. I would prefer
> to use the built-in functionality of the NAS to fall back from a primary
> to secondary or tertiary auth/accounting servers.
>
> This whole setup would be far simpler and more robust if I could just do
> master-master replication with the MySQL servers. Oh well.

master-master =3D bad-bad

Dont even consider it!!!!!!!!! MySQL's master-master implimentation is=20
completely brain dead and WILL give you corrupt data is a very short time=20
period (It doesn't do ANY locking across the cluster!!!).

If you must use Mysql, use Master-Slave replication for as many authorizati=
on=20
servers as you wish, but configure only ONE radius server to actually write=
=20
accounting to the master database and all the others to use radrelay (or=20
radsqlrelay) to get the data to that server

Cheers
=2D-=20

Peter Nixon
http://www.peternixon.net/
PGP Key: http://www.peternixon.net/public.asc

--nextPart2309267.afQ3TzV83o
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBFr/JuAcdsUt9pJjwRAsr3AJ90fAoVLkb3EXLmsJVbSKo9xIOHegCg oimm
jKBRdbNIhM7GtIct4NOkmCs=
=w7d4
-----END PGP SIGNATURE-----

--nextPart2309267.afQ3TzV83o--

--===============0961500739==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--===============0961500739==--