Hi,

[Apologies in advance - I know this is not a Firebird list, but here are many Firebird DB users that could possibly comment.]

Has anybody here used any Firebird database replication software?

I've been reading up on it a bit, and there seems to be more options available that I expected. Has anybody tried any of them, and could possibly give some comment.

IBReplicator - commercial, cross-platform, full-featured http://www.ibphoenix.com/products/software/ibreplicator

FiBRE - open source, cross-platform
http://fibre.sourceforge.net/

FBReplicator - open source
http://www.meta.com.au

IBO Replication Module - Delphi/C++ Builder components http://www.ibobjects.com/iborpl.html

ReplicadorBR - open source
http://sourceforge.net/projects/replicadorbr/

Replicador Firebird - freeware
Originally available from http://replicadorfirebird.ich.pro.br/ Download (2.2MB zip file) from:
http://firebirdfaq.org/files/Replicador_Firebird_1.0.12.7z

CopyCat (components) and CopyTiger (application) - commercial http://www.microtec.fr/copycat/

ININ Replication Manager - commercial
http://www.inin.hr/

Daffodil Replicator - commercial
http://enterprise.replicator.daffodilsw.com/index.html

DB Replicator - open source fork of Daffodil
http://dbreplicator.org/

DBRE - open source, supports Firebird and MySQL
http://dbre.sourceforge.net/

IB LogManager - not a real replicator, but helps setting up a hot-standby environment easily:
http://www.upscene.com/products/audit/iblm_main.htm Demo Flash movie available here:
http://www.iblogmanager.com/download/demos/iblm/iblm_hotstandby.htm

SymmetricsDS - open source, cross platform, supports various DBMS: http://www.symmetricds.org

Frext - Doesn't seem to have started yet, good research info. http://frext.sourceforge.net/

Regards,
- Graeme -

Do you want replication or clustering ?

I have looked into this problem several times.

From my point of view, all of these solutions suffer from the same problems:

a) they slow down the database.
and
b) if the database structure changes often, it is a pain to maintain.

The only correct way to implement this is in the server engine itself; until that is done, these are crude and makeshift solutions. (e.g. Postgres got it correct with their 'slony' replication)

IMHO You're better of using nbackup to rebuild the database remotely. At the very least, that requires no extra triggers, log tables and whatnot, and will not slow down the database.

If your database structure is fixed, you don't update very often, the tools you mention can be acceptable. If so, then I'd recommend going with the firebird native tools, such as ibreplicator.

Michael.

I did my replication service application 7 years ago, its still work. I used firebird 1.5.6. On center store has a server computer, and this db work on LAN more then clients same time. 8 store in different cities. All off them has a two way replication. Main store sent data to first store, maybe same time or any time first store can sent data to main store too. Connection is 8mb adsl line. 2 store has 4mb adsl line. if any db(store) has a change record(s) (insert, update, delete) sent to all others dbs. So each store has a same ALL datas, and see just self data.

I recommend,
-)need good work on developing tables and stores unique keys -)use http://www.winton.org.uk/zebedee/index.html for compress data and secure datas
-)if you use joined tables, don't forget replication tables order -)use commit after minimum records post. example: after 5-10 records, 'cos if has a problem, in 999. record have to rollback all of them, and restart from 1. this is lost time and make problem. -)create replication user and make roles

FreeMan wrote

I did my replication service application 7 years ago, its still work. I

Thanks for letting me know. It sounds promising.

Regards,
- Graeme -