RE: [RadiusNT] Redundancy
Troy Settle ( (no email) )
Thu, 24 Feb 2000 20:57:33 -0500
> Troy Settle wrote:
> >
> > I would not recommend doing a nightly transfer unless you're short on
> > bandwidth, or don't care about concurrency control. A transactional
> > replication would be much better for this. I'm doing it now, and it's
> > actually very light on the CPU and Bandwidth.
> >
> > Anyways, you probably want all the tables except the CALLS
> table, though I
> > didn't try leaving any out to be sure.
> >
> > You'll also need to copy all the stored procedures and views
> before you'll
> > be functional.
> >
> > If accounting is important for you, you'll want to send
> accounting info to a
> > seperate DSN that points to your primary SQL database.
>
> If all you want it authentication, then don't replicate the billing
> tables.
> Check the RadiusNT documentation and only replicate the tables listed in
> there. That way when you do billing, it doesn't try and move all that
> information to the other server.
>
I posted that with RadiusNT in mind only, expecting that the reader would
see "all the tables" and assume those relating to RadiusNT only, and not try
to duplicate the billing tables (that would get messy).
-Troy
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart