> --- Stanislav Sinyagin <[EMAIL PROTECTED]> wrote:
> 
>> It would be great to implement a new option in policyd.
>> Technically it should not be difficult.
>> 
>> The new option would list a backup MySQL server/dbname/user/password,
>> and if it's specified, every INSERT statement is duplicated on that
>> server. 
>> 
>> This would allow an elegant redundant solution: two policy gateways
>> would update each other's SQL databases, without the need of complex
>> database synchronization.

Well, IMO MySQL DB replication is not too complex to setup. We have it
running in a Dual Master setup (both databases are in use by 2 MTA's) so
both MTA's share the same information: if either MX goes down, the other
still works with all information.

I think you just have to plan your replication carefully so that you
don't get duplicate id's. But then, Policd doesn't use id's in it's
tables so in this case it is a non-issue...


Grts,
Rob

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
policyd-users mailing list
policyd-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/policyd-users

Reply via email to