(RADIATOR) How does SQL Fallover work?

[Dan Vande More]

If the radius server cannot make a establish an application level(or below) connection to the database server, for whatever reason, it will try an alternative, or try again.
If the database gives an error, it seems to me radiator denies the authentication request but does not assume anything is wrong with the database.
This is the observed behavior of 3.3.1.
I understand the reasoning for your question, and hope this helps.
If you need something to monitor hardware failure, application failure, etc., I suggest trying Big Brother/Nagios, or any number of snmp applications.

Dan Vande More

-----Original Message-----
From: William Hernandez [mailto:whr at essnet.com]
Sent: Thursday, September 11, 2003 9:53 AM
To: 'Radiator'
Subject: (RADIATOR) How does SQL Fallover work?


Hello everyone,

The Radiator 3.3.1 manual states in Section 6.28 <AuthBy SQL>

"AuthBy SQL is tolerant of database failures. If your database
server goes down, Radiator will try to reconnect to a database as
described above, starting again at the first database you
specified."

What does "server goes down" mean? Does it refer to a hardware
failure? Does it mean the SQL Server application goes down? Does
it mean that the particular database for some reason becomes
unavailable and a connection is not possible although the SQL
Server is still running? Does it mean that a connection was made,
but there was an error/problem with the SQL query? All of the
above?

Thanks in advance,

William Hernández

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.