Subject | RE: [firebird-support] Interested in 'real life' database redundancy setup info |
---|---|
Author | Alan McDonald |
Post date | 2004-06-14T14:36:21Z |
> We are considering Firebird 1.5 for a mission critical, on-line InternetYou must be expecting about 50,000 hits an hour with config.. Are you?
> based system, that requires 99.9% uptime. I know that this might be a
> pipe-dream, however it would appear that Firebird has what it takes to do
> this. Here's our planned setup so far:
>
> 1. 3 x Dell PowerEdge servers running RedHat Linux 9, all with RAID 5
> drive arrays, collocated at a major facility here in Phoenix, Arizona
>
> 2. Firebird 1.5 Super Server running on each box. Our database is
> about 200 tables in size, with stored procs, triggers, etc.
>
> 3. Apache/PHP for the web application to work these databases.
>
> I know that Firebird has a 'Shadow' facility that will make a
> shadow version
> of the database, however I understand that you don't want to try
> and do this
> with a network connection between the boxes.
>
> Therefore, if I want to construct a way to 'load balance' on this array of
> computers, what would be the best way to look at this?
>
> Also if I need to make a mirror'd copy of the database on a computer at a
> different location (as a fall back if something in the main site
> goes down),
> are there any tested synchronization systems available for Firebird that
> anyone can recommend?
>
> Thanks
> Myles
>
replication solutions are quite numerous - check ibphoenix.com
Also consider write ahead logs - see IBLogmanager for that.
Shadowing IMO is a waste of time and you're write - they have to be on local
hard drives.. if you get a corruption in one copy it's there in the other
immediately.. :-)
Alan