Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5F7649FB7C9 for ; Tue, 13 Feb 2007 05:27:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 26211-09 for ; Tue, 13 Feb 2007 05:27:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from power2u.goelsen.net (mail.goelsen.net [195.202.170.130]) by postgresql.org (Postfix) with ESMTP id 892A69FB7D0 for ; Tue, 13 Feb 2007 05:27:30 -0400 (AST) X-Envelope-From: michael.monnerie@it-management.at Received: from localhost (localhost [127.0.0.1]) by power2u.goelsen.net (Postfix) with ESMTP id B78E66F0C0 for ; Tue, 13 Feb 2007 10:27:25 +0100 (CET) Received: from power2u.goelsen.net ([127.0.0.1]) by localhost (power2u.goelsen.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02967-03 for ; Tue, 13 Feb 2007 10:27:14 +0100 (CET) X-Envelope-From: michael.monnerie@it-management.at Received: from mailsrv.i.zmi.at (h081217116113.dyn.cm.kabsi.at [81.217.116.113]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by power2u.goelsen.net (Postfix) with ESMTP id 8F33C53561 for ; Tue, 13 Feb 2007 10:27:04 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: online tape backup Date: Tue, 13 Feb 2007 10:26:29 +0100 User-Agent: KMail/1.9.5 References: <200702091951.14100.ejortegau@cable.net.co> In-Reply-To: <200702091951.14100.ejortegau@cable.net.co> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1804854.CE2uzbVYdj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200702131027.02556@zmi.at> X-Virus-Scanned: amavisd-new at goelsen.net X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=BAYES_50, FORGED_RCVD_HELO, SPF_HELO_PASS X-Spam-Level: X-Archive-Number: 200702/173 X-Sequence-Number: 24638 --nextPart1804854.CE2uzbVYdj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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=20 I'm thinking of switching from currently pg_dump on all databases to=20 using the concept of base+WAL backup. What we did until now was (not using WAL) =2D pg_dump for each DB =2D vacuum full analyze for each DB after backup =46rom what I understand, if I run a vacuum, the WAL logs will be=20 enormous, as they do not simply store the vacuum command itself, but=20 every single operation done on the db. If that's true, running vacuum before the base backup could be better,=20 as there are less WAL logs to store, making the backup smaller, right? mfg zmi =2D-=20 // 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 --nextPart1804854.CE2uzbVYdj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBF0YRmui0GDxxv5rARArjvAJ45NHTrGtn6MV9yykk1M51SEtl6QgCgrD4C PRFzZeVFhAx2KNKYdrTzuTg= =rDUU -----END PGP SIGNATURE----- --nextPart1804854.CE2uzbVYdj--