> > > > > 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 e.g. > A-B-C) > > and simultaneously D is s primary to E,F,G ? > I have no idea if it can work with built-in replication at all. > > In any case the scheme doesn't look robust because of single points of > failure in D and F but perhaps it can be good for something else. > Replication is > used for a definite purpose, not just "because we can".
My goal is indeed replication without a single point of failure. It the above would have been possible (replication from two masters), than the following would also have been possible : H would be a replica in the case when nothing else works anymore, A,B,D have failed D->H is not necessary needed in this case [image: image.png] How do the transaction logs are generated? Do they depend on the primary guid? If not, that shall work... Am Mo., 1. Nov. 2021 um 12:06 Uhr schrieb Dimitry Sibiryakov < s...@ibphoenix.com>: > Pro Turm wrote 01.11.2021 11:47: > > Thanks. Could you please give some more words about this case? > > > > 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 e.g. > A-B-C) > > and simultaneously D is s primary to E,F,G ? > > I have no idea if it can work with built-in replication at all. > > In any case the scheme doesn't look robust because of single points of > failure in D and F but perhaps it can be good for something else. > Replication is > used for a definite purpose, not just "because we can". > > -- > 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
