> > > Which means cascading could be quite vulnerable. What is then the > quickest > > possible way to connect A to C in the above case? > > Drop database C, recreate replica from scratch. > Is the following constellation also possible? A--\ /--E B---D------F C--/ \--G That is that D replicates A,B,C (which share the same content) and simultaneously is s primary to E,F,G ?
> > > > Restarting the servers: are there some performance issues expected > due to > > > restarting (looising data, long-time unavailability etc.) ? > > > > It depends. > > > > Could you please elaborate more on that ? > > Performance issues, data losses and recovery time highly depends on the > nature of the disaster that has made the recovery needed, replication > settings > and other factors. Do you have more concrete measurements or cases? And some times (best, worst, average) according to the amount of data being replicated? Particularly I'm interested in asynchronous replication only. Am Mi., 27. Okt. 2021 um 14:49 Uhr schrieb Dimitry Sibiryakov < s...@ibphoenix.com>: > Pro Turm wrote 27.10.2021 14:39: > > Which means cascading could be quite vulnerable. What is then the > quickest > > possible way to connect A to C in the above case? > > Drop database C, recreate replica from scratch. > > > > Restarting the servers: are there some performance issues expected > due to > > > restarting (looising data, long-time unavailability etc.) ? > > > > It depends. > > > > Could you please elaborate more on that ? > > Performance issues, data losses and recovery time highly depends on the > nature of the disaster that has made the recovery needed, replication > settings > and other factors. > > -- > WBR, SD. > > > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel >
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
