>
> 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.

They have all that, and yet want to have it double. Their IT guys
also don't really see the point, but their upper managment wants it,
since they had a crash about a year ago on their previous server
(which was a windows server with Mssql2000 DB) and that costed them a
lot, hence the complete switch to Linux and firebird (well they had a
couple more reasons, but that would bring us too much OT ;-))

>
> >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...

Yep, they know.

>
> >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?
> --

No the Firebird DB lies on a different device that gets mounted both
when booted master as when server, only the path differs.
(eg /DB/MYDB.FDB vs /mnt/master/DB/MyDB.FDB)
And firebird is installed on both master as slave boot (on each
machine)

Dirk Naudts.