Thread: Real time backup options.

I run a modest postgres database manualy edited (via a web fron end) by
3-4 people. So the number of transactions is comparativly low.

I'd like to set up some sort of real time backups

The problem is I only have one server to run postgers on so I suspect its
a bad idea to run two instances of postgres one running on a local hard
disk the other on a NAS disk and replecate between the two.

In terms of disaster recovery I don't need anything fancy.  Just the
ability to restore from a weekly pg_dumpall then replay the subsiquent
transactions from a NAS disk.

What options should I look at?  Am I reduced to turning the logging up to
11 and stripping out the non-SQL statements?

--
Michael
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Michael John Lush PhD            Tel:44-1223 492626
Bioinformatician
HUGO Gene Nomenclature Committee    Email: hgnc@genenames.org
European Bioinformatics Institute
Hinxton, Cambridge
URL: http://www.genenames.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>>On Feb 8Gmail - [NOVICE] Real time backup options. - shoaibmir@gmail.com, 2008 5:22 PM, Michael Lush <mjlush@ebi.ac.uk> wrote:


Did you look at using PITR as an option, specifically using record based log shipping with 'pg_xlogfile_name_offset()' as that might help in your case. You can find details about that on --> http://www.postgresql.org/docs/current/static/warm-standby.html

--
Shoaib Mir
Fujitsu Australia Software Technology
shoaibm[@]fast.fujitsu.com.au