-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Is it possible to do a full file system level backup of the data
directory, say once a week, and differentials or incrementals daily?
...
taken, so a trigger-based or WAL-based system is necessary.
...
SQL-level differentials would be
Is it possible to do a full file system level backup of the data
directory, say once a week, and differentials or incrementals daily?
I'd love to be able to do this, but you can't do it usefully at a
file-system level. There's too much churn in the data files for even a
binary diff to be
On 10/20/2011 02:00 AM, Bob Hatfield wrote:
Is it possible to do a full file system level backup of the data
directory, say once a week, and differentials or incrementals daily?
I'd love to be able to do this, but you can't do it usefully at a
file-system level. There's too much churn in the
On 10/13/2011 05:30 AM, Bob Hatfield wrote:
Is it possible to do a full file system level backup of the data
directory, say once a week, and differentials or incrementals daily?
I'd love to be able to do this, but you can't do it usefully at a
file-system level. There's too much churn in the
Bob Hatfield wrote:
Is it possible to do a full file system level backup of the data
directory, say once a week, and differentials or incrementals daily?
I'm wondering if there are files that would normally be removed that a
restore: Full then diff/inc would not remove and perhaps
If you drop or truncate a table between the full and the incremental backup,
will that file be resurrected?
Such resurrected files will not disturb PostgreSQL, but if you keep them
around, you might end up with a lot of dead files if you have to restore a
couple of times.
That makes
Is it possible to do a full file system level backup of the data
directory, say once a week, and differentials or incrementals daily?
I'm wondering if there are files that would normally be removed that a
restore: Full then diff/inc would not remove and perhaps
corrupt/confuse things.
Process:
As there's one file for each object, a single update on each would make you
to copy the all the file again. I heard there was tool to make differentiel
copy of a part of a file but I don't know if it's really efficient.
Anyway, a better way for you would be to do a regular backup (with
Anyway, a better way for you would be to do a regular backup (with
pg_start_backup, copy and pg_stop_backup) and then use wal archive_command to
keep the xlogs between 2 full backups.
Thanks Julien. Can pg_start/stop_backup() be used for regular full
file system backups? All of the
On Thu, Oct 13, 2011 at 12:04 AM, Bob Hatfield bobhatfi...@gmail.comwrote:
Anyway, a better way for you would be to do a regular backup (with
pg_start_backup, copy and pg_stop_backup) and then use wal archive_command
to keep the xlogs between 2 full backups.
Thanks Julien. Can
On October 12, 2011 03:04:30 PM Bob Hatfield wrote:
Anyway, a better way for you would be to do a regular backup (with
pg_start_backup, copy and pg_stop_backup) and then use wal
archive_command to keep the xlogs between 2 full backups.
Thanks Julien. Can pg_start/stop_backup() be used
The base backup necessary to initialize a warm standby server is a full file
system backup of the database, which can also be used for restores to any
point in time after the base backup is completed, assuming you also have all
the archived WAL files.
Thanks to both of you. I currently
12 matches
Mail list logo
