[RADIATOR] Two session DB's updated on flight?

[Toomas Kärner]

Hello Hugh,

This was one of our ideas also... easiest and possible to understand
what the .... is going on here, later.

Thanks.
Toomas


Tuesday, August 12, 2008, 6:35:10 AM, you wrote:

> Hello Toomas -

> Probably simplest to proxy copies ot the accounting requests to a  
> second instance of Radiator to update the second session database.


> ......

> # define AuthBy RADIUS

> <AuthBy RADIUS>
>         Identifier ForwardAccountingForSessionDatabase
>         IgnoreAuthentication
>         IgnoreAccountingResponse
>         Host ....
>         Secret .....
>         .....
> </AuthBy>

> ......

> # modify your Realm(s) and/or Handler(s)

> <Handler .......>

>         AuthByPolicy ContinueAlways

>         AuthBy ForwardAccountingForSessionDatabase

>         ......

> </Handler>

> .....


> Otherwise, use the tools for your database to replicate the second  
> session database.

> regards

> Hugh


> On 11 Aug 2008, at 21:25, Toomas Kärner wrote:

>> Hi all,
>>
>> We are migrating from one DB cluster to another and during it we need
>> to replicate sessionDB into both clusters so we need a configuration
>> that keeps two <SessionDatabase SQL>'s updated.
>> I have some ideas but they are ugly. Any ideas from you?
>>
>> Rgds.
>> Toomas
>>
>>
>>
>>
>>
>> _______________________________________________
>> radiator mailing list
>> radiator at open.com.au
>> http://www.open.com.au/mailman/listinfo/radiator



> NB:

> Have you read the reference manual ("doc/ref.html")?
> Have you searched the mailing list archive (www.open.com.au/archives/ 
> radiator)?
> Have you had a quick look on Google (www.google.com)?
> Have you included a copy of your configuration file (no secrets),
> together with a trace 4 debug showing what is happening?
> Have you checked the RadiusExpert wiki:
> http://www.open.com.au/wiki/index.php/Main_Page