On 10 Feb 2005 at 11:11, dirknaudts wrote:

>> As you described below, you actually need not replication, but
>high
>> availability of database.
>
>Yes, and it's most current data, it's a realtime auctioning system ,
>so every auction transaction (=Buyer purchase) is important, as well
>as available supply. The main thing is that the auction has to be able
>to continue, only a small hickup may be the result of a server crash !

It is off-topic for this list, but... What kind of crash do they
expect?
Disc failure can be prevented with RAID. RAM - ECC or something
like this. Power - UPS and dual supply unit.
I really don't know what can oppose a tsunami or plane crash.

>Well both servers are dual boot (master and slave) so when the master
>crashes, they restart the slave as master, which gives it the master's
>ip address. I did suggest for the software to switch automatically,
>but they (our customer) prefered it to be a manual switch.

It also require human watching. Besides, reboot of modern Windows
or Linux server takes some minutes...

>That would make the transition master/slave lighter, true, but I'd
>have to build a trigger in it so client apps would be aware of the
>switch, and customer wanted the switch to be manual, not
>automatically, with full restart.

There is a problem of recovery after the crash. How you are going
to create new slave database after switching?
--
SY, Dimitry Sibiryakov.