Thread: Replication

I'm creating a DB that is extremeley important to have running all the
time.  Not for the importance of the data, but rather to keep the
maximum uptime for the users.  The db actually gets dropped, and
recreated and 1,000,000-ish records inserted every night.  I would like
to create an identical db on seperate hardware that, in the event of
hardware failure, the users could use while the hardware is getting
replaced.  What is the best method (considering no money can be spent
other than my time) to do this?



--Bryan

Hi Bryan,

Bryan Irvine wrote:

>I'm creating a DB that is extremeley important to have running all the
>time.  Not for the importance of the data, but rather to keep the
>maximum uptime for the users.  The db actually gets dropped, and
>recreated and 1,000,000-ish records inserted every night.  I would like
>to create an identical db on seperate hardware that, in the event of
>hardware failure, the users could use while the hardware is getting
>replaced.  What is the best method (considering no money can be spent
>other than my time) to do this?
>
>
>
Have a look at pgrelicator http://pgreplicator.sourceforge.net/ or
postgreSQL-R
http://gborg.postgresql.org/project/pgreplication/projdisplay.php

Cheers

--
Noel Faux
Department of Biochemistry and Molecular Biology
Monash University
Clayton 3168
Victoria
Australia