| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dan Gorman <dgorman(at)hi5(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PITR Backups |
| Date: | 2007-06-22 00:26:45 |
| Message-ID: | 9761.1182472005@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Dan Gorman <dgorman(at)hi5(dot)com> writes:
> All of our databases are on NetApp storage and I have been looking
> at SnapMirror (PITR RO copy ) and FlexClone (near instant RW volume
> replica) for backing up our databases. The problem is because there
> is no write-suspend or even a 'hot backup mode' for postgres it's
> very plausible that the database has data in RAM that hasn't been
> written and will corrupt the data.
I think you need to read the fine manual a bit more closely:
http://www.postgresql.org/docs/8.2/static/backup-file.html
If the NetApp does provide an instantaneous-snapshot operation then
it will work fine; you just have to be sure the snap covers both
data and WAL files.
Alternatively, you can use a PITR base backup as suggested here:
http://www.postgresql.org/docs/8.2/static/continuous-archiving.html
In either case, the key point is that you need both the data files
and matching WAL files.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-22 01:51:11 | Re: Data transfer very slow when connected via DSL |
| Previous Message | Dan Gorman | 2007-06-21 23:31:32 | PITR Backups |