pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@it-management.at>
To: pgsql-admin@postgresql.org
Subject: Re: online tape backup
Date: Tue, 13 Feb 2007 10:26:29 +0100
Message-ID: <200702131027.02556@zmi.at> (raw)
In-Reply-To: <200702091951.14100.ejortegau@cable.net.co>
References: <200702091951.14100.ejortegau@cable.net.co>

On Samstag, 10. Februar 2007 01:51 Eduardo J. Ortega wrote:
> 1) pg_start_backup
> 2) tar to my tape device /data/postgresql excluding
> /data/postgresql/pg_xlog 3) pg_stop_backup
> 4) delete WAL files under /data/pg_trans_log/ (which is the directory
> to which archive_command copies my archived WAL files) with name
> "smaller" than the name of the last 000*.backup
> 5) append to previously created tar on the tape the WAL
> directory /data/pg_trans_log/

Dear all, I'm replying to this message because it's a good start, and 
I'm thinking of switching from currently pg_dump on all databases to 
using the concept of base+WAL backup.

What we did until now was (not using WAL)
- pg_dump for each DB
- vacuum full analyze for each DB after backup

From what I understand, if I run a vacuum, the WAL logs will be 
enormous, as they do not simply store the vacuum command itself, but 
every single operation done on the db.

If that's true, running vacuum before the base backup could be better, 
as there are less WAL logs to store, making the backup smaller, right?

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0676/846 914 666                      .network.your.ideas.
// PGP Key:        "curl -s http://zmi.at/zmi4.asc | gpg --import"
// Fingerprint: EA39 8918 EDFF 0A68 ACFB  11B7 BA2D 060F 1C6F E6B0
// Keyserver: www.keyserver.net                   Key-ID: 1C6FE6B0

view thread (6+ messages)  latest in thread

Message-ID: <200702131027.02556@zmi.at>
Permalink:  ../200702131027.02556@zmi.at/
Also on:    postgresql.org/message-id/200702131027.02556@zmi.at

 · 

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-admin@postgresql.org
  Cc: michael.monnerie@it-management.at
  Subject: Re: online tape backup
  In-Reply-To: <200702131027.02556@zmi.at>

* 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