Re: backup server

Mitchell B. Wagers ( )
Wed, 25 Feb 1998 05:53:10 -0800

Use an SQL Trigger to update your secondary database whenever the primary is
updated. This cuts the duplications to a minimum because if the primary goes
down it doesn't effect the secondary, while the changeover to the secondary
Radius Server by the NAS's happens at the same time...Pretty streamlined and
slick. :)

At 07:31 AM 2/25/98 -0500, you wrote:
>At 12:01 AM 2/25/98 -0800, you wrote:
>>> Is it possible to write the SQL database to a RADIUS text file and use that
>>> on the backup machine?
>>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.
>The problem with that approach is that our SQL database resides on our main
>RADIUS server. If IT is down for any reason, RADIUS is also down.
>Replicating the database isn't without problems, either, as we found out
>yesterday. It's fairly easy to have callers shown as "online" when they're
>not due to the manner in which that information is stored in the tables.
>The users cannot log on due to their being "already online".
> <<>>
> ----------------------------------------------------------
> RadiusNT Mailing List