RE: sqlippool



Yes. Redundancy (high availability) will have to be built on the database
side. You can't configure redundancy of sql instances inside sqlippool
module definition.

Ivan Kalik
Kalik Informatika

Dana 4/7/2008, "Laar, Johan van de" <Johan.van.de.Laar@tnf.nl> piše:

>OK, but with authentication or accounting you can use something like:
>
>redundant {
>  # Try db 1
>  sql_MYSQL_1
>
>  #try db 2
>  sql_MYSQL_2
>}
>
>It seems like this is not possible with sql ippool. Am I right?
>
>
>Johan van de Laar
>
>-----Oorspronkelijk bericht-----
>Van: freeradius-users-bounces+johan.van.de.laar=tnf.nl@lists.freeradius.org [mailto:freeradius-users-bounces+johan.van.de.laar=tnf.nl@lists.freeradius.org] Namens Ivan Kalik
>Verzonden: donderdag 3 juli 2008 18:33
>Aan: FreeRadius users mailing list
>Onderwerp: Re: sqlippool
>
>Yes. You will need to use database management to replicate them and keep
>them in sync.
>
>Ivan Kalik
>Kalik Informatika ISP
>
>
>Dana 3/7/2008, "Laar, Johan van de" <Johan.van.de.Laar@tnf.nl> piše:
>
>>Is it possible to use two sql instances (sql-instance-name) for the same IP pool? (with version 2.0.5)
>>To achieve some redundancy when one of the databases crashes.
>>
>>Thank you in advance.
>>
>>Johan van de Laar
>>
>>
>>
>
>-
>List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
>-
>List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
>




This archive was generated by a fusion of Pipermail (Mailman edition) and MHonArc.