pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dan Gorman <dgorman@hi5.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PITR Backups
Date: Thu, 21 Jun 2007 20:26:45 -0400
Message-ID: <9761.1182472005@sss.pgh.pa.us> (raw)
In-Reply-To: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com>
References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com>
Dan Gorman <dgorman@hi5.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
view thread (38+ messages) latest in thread
Message-ID: <9761.1182472005@sss.pgh.pa.us> Permalink: ../9761.1182472005@sss.pgh.pa.us/ Also on: postgresql.org/message-id/9761.1182472005@sss.pgh.pa.us ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-performance@postgresql.org Cc: tgl@sss.pgh.pa.us, dgorman@hi5.com Subject: Re: PITR Backups In-Reply-To: <9761.1182472005@sss.pgh.pa.us> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox