Re: Back up server

Stephan Malkmus ( )
Thu, 26 Feb 1998 12:35:50 +0100

At 02:30 AM 2/26/98 -0800, you wrote:
>Secondary machines is the whole point of supplying that information to your
>NAS...The best way (In my opinion) is to specify backup radius servers in
>your NAS's, not on the database itself. I have a previous posting about the
>SQL/Replication issue.

We specified a secondary radius server on the NAS that point's (the radius
secondary) to another database - this works pretty good if the first crashes.
But we want to point it to the same database as the first radius server and
only when the SQL Server is down it should automaticly change to the second
database which was replicated from the SQL server. I hope it is clear what
I wanted to say
because I am german and not sure if I translated it well.

Stephan Malkmus (
>At 11:06 AM 2/26/98 +0100, you wrote:
>>>Just install RadiusNT on a second machine and point it to your
>>>same SQL Server. That will give you redundancy on the RADIUS
>>>level. You can use SQL Server's replication if you want to replicate
>>>the database itself to another server.
>>When I replicate the server how can I tell Radius to use the
>>DSN that points to the other SQL machine or does radius do
>>this by itself or can it be configured in the DSN to use
>>an alternative database if the first doesn't work.
>>Stephan Malkmus (
>>>Dale E. Reed Jr. (
>>> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
>>> Internet Solutions for Today |
>>> ----------------------------------------------------------
>>> RadiusNT Mailing List
>> ----------------------------------------------------------
>> RadiusNT Mailing List
> ----------------------------------------------------------
> RadiusNT Mailing List