27 Feb
2004
27 Feb
'04
12:22 a.m.
Nils Ohlmeier wrote:
How about i selectivly replicate the tables or configure the backup to
use different tables for the subscriber data?
I will setup a test system for this, make some experiments and read
docu and source.
-- Arnd
On Thursday 26 February 2004 22:40, Arnd Vehling
wrote:
ARGH, NO :) I ment the "register" message.
Nils Ohlmeier wrote:
INVITE and subscriber table??? Yes, comitted. But the replicated data will not be
read in by the backup
server.
Mhh, seems like i didnt really understood what t_replicate does.
I thought "t_replicate" will replicate all invites to a failover box
so the primary and secondary are synced in terms of subscribed
users?! I thought
t_replicate will do this. But if not i either restart ser as
suggested or patch it so it will re-read the subsriber table if i send
it a SIGHUP or a something via the fifo.
Two choices:
- either use DB replication and restart SER on failover to re-readin the
location table on startup
- t_replicate all successfull REGISTER and omit DB replication, but beware of
the possible drawbacks.