I intend to mirror a 4.25 client server database during live service
onto a second identical system with a different IP. So that an instant
switch to system 2 is possible if system 1 breaks.

What would be the best way to do this?

Arnd

Arnd,

<< I intend to mirror a 4.25 client server database during live service onto
a second identical system with a different IP. So that an instant switch to
system 2 is possible if system 1 breaks.

What would be the best way to do this? >>

The easiest way to do so is via the triggers - just dump each row insert,
update, delete, etc. over to the backup server.  However, the tricky part is
transactions - just because a row is inserted, updated, or deleted and
causes the trigger to fire does not mean that the row was actually
committed.  I'm not sure if there's a way to solve that issue, either,
without modifying the server code directly or just using an external
mirroring service for the database table files.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> The easiest way to do so is via the triggers - just dump each row insert,
> update, delete, etc. over to the backup server.  However, the tricky part is
> transactions - just because a row is inserted, updated, or deleted and
> causes the trigger to fire does not mean that the row was actually
> committed.  I'm not sure if there's a way to solve that issue, either,
> without modifying the server code directly or just using an external
> mirroring service for the database table files.
>

thank's.

I will start the way you indicated and see where I will end up as  I
cannot think of a better way.

Best Regards

Arnd