Now, my topic is slightly misleading... And this isn't so much a 'support it's broken' request as a 'support is it possible' query.
[Note, I did a search for this, and couldn't find anything recent enough to be relevant. My apologies if this exists already]
What I am wanting to do is configure two anope's (latest versions) to act as a backup to each other on the same network.
They would both be named services.network.com, so they couldn't be online at the same time.
In the past, I've had a script regularly copying the .db files from the master to the slave, the slave has started in readonly mode and staff have squitted the slave when the master becomes available again.
What I want to know, is if I can run both services as read-write, using an SQL db as the common point.
I figure that if one drops, the other will pick up, reading from the SQL and thus starting where the others left.
Essentially I have three questions:
1) If services starts and fails to connect, does it read the SQL and write it to it's .db files?
2) If services can't reach the SQL server, will it print and error and continue to connect, or will it fail and stop again?
3) If there is a mismatch between SQL and the .db files, is one taken preferentially? IE, if an oper deletes a channel or nick, it will remove from SQL. If it exists in a .db on the other server, will it be readded to SQL upon the failover?