Re: Database backup mechanism

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: RaviKumar(dot)Mandala(at)versata(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Database backup mechanism
Date: 2007-02-09 12:17:49
Message-ID: 45CC666D.8050708@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

RaviKumar(dot)Mandala(at)versata(dot)com wrote:
> We have a requirement to deal with large databases of the size Terabytes
> when we go into production. What is the best database back-up mechanism
> and possible issues?

It depends.

Make sure you read Chapter 23. Backup and Restore of the user manual:

http://www.postgresql.org/docs/8.2/interactive/backup.html

It discusses pg_dump and restore, as well as file system level backup.
You'll probably want to set up continuous archiving, which allows you to
take a file-system level backup without shutting down the database.

> What about taking zipped back-up of the database directory? We tried this
> out but the checkpoint data in pg_xlogs directory is also being backed-up.
> Since these logs keeps on increasing from day1 of database creation, the
> back_up size if increasing drastically.

The amount of WAL files in pg_xlog directory is controlled by the
checkpoint_segments configuration parameter.

> Can we back-up certain subdirectories without loss of information or
> consistency..?

No.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Doug Knight 2007-02-09 13:16:14 Re: Database backup mechanism
Previous Message Pavel Stehule 2007-02-09 11:40:59 Re: Proposal: TABLE functions