Den 2011-08-08 18:39 skrev Dimitry Sibiryakov såhär: > 08.08.2011 18:33, Kjell Rilbe wrote: >> This copy should be as up to date as possible, >> transaction by transaction. >> >> Are there no replicators that can do this? > > Yep. > All Firebird replicators that I know are asynchronous. It means that > there is a > possibility to loose some data on crash. The possibility can be small, as > well as the lost > data amount, but never is zero. > Shadow represents synchronous replication with guaranteed zero data > losses.
I see. But I assume the replicators will not make the copy corrupt or update it in incorrect order or something. On a crash, the replication target will be a working copy of the source, but with N transactions missing, where N is "small" but non-zero. Any indication of how large the lag (N) could be? Can it grow without bounds if the server load is high? Kjell -- -------------------------------------- Kjell Rilbe DataDIA AB E-post: kj...@datadia.se Telefon: 08-761 06 55 Mobil: 0733-44 24 64 ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
