Ok! Its a good tool, but for Production Database I think it is not
recommended.
Only using pg_dump for the second backup plain.
Suppose that you backed up at 6:00am and at 9am happened a crash on the
server.
In this case, I would lost data between that time, 3 hours of information.
For production databases, my plan is to do phisical backup including WAL.
If a crash happen, I can restore the datafiles and recover applying the
WAL logs until the last file was generated.
As Oracle does in this type of crash.
My doubt is that I am not getting apply the WAL files on recover stage.
Any other suggestion?
Thanks for your help
Aaron Bono escreveu:
> On 7/11/06, *Burbello* <burbello3000@yahoo.com.br
> <mailto:burbello3000@yahoo.com.br>> wrote:
>
> I need to test and create a procedure to restore
> databases.
>
>
> Why not just use pg_dump?
>
> See http://manual.intl.indoglobal.com/ch06s07.html
> <http://manual.intl.indoglobal.com/ch06s07.html> - it's really easy.
> This is how we copy from production to testing and development and how
> we do nightly backups.
>
>
> ==================================================================
> Aaron Bono
> Aranya Software Technologies, Inc.
> http://www.aranya.com
> ==================================================================