Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCCJh-0004AX-Cf for pgsql-admin@arkaria.postgresql.org; Wed, 21 Aug 2013 17:35:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VCCJg-00073h-SI for pgsql-admin@arkaria.postgresql.org; Wed, 21 Aug 2013 17:35:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCCJf-00073a-QO for pgsql-admin@postgresql.org; Wed, 21 Aug 2013 17:35:31 +0000 Received: from mail-la0-x231.google.com ([2a00:1450:4010:c03::231]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCCJc-0003bK-85 for pgsql-admin@postgresql.org; Wed, 21 Aug 2013 17:35:31 +0000 Received: by mail-la0-f49.google.com with SMTP id ev20so595659lab.22 for ; Wed, 21 Aug 2013 10:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=uk+hL4+Rx2xhRNtSN4QLyUPwYoArAYPPvn4jzxCFHB4=; b=KiBOzF60M0+KlMIH4WsLxYmnvAPmCdHzcJ9FNvD2caL2XGghVdMANxh69a5LoNgOIb cDl5paEcrwdU0Lmj+lIcEKwPRz5pjspckiRPXQ6Npae5ulPz8oWZKL4lIMtSD0nu3q55 LcuRXNlGd9XAExXwltg69qPBdCin7TQdStYTZ1hcrl++/c30RbkgxOTe0z7OXFSu5/4h xN2rcqYl92V0bkJzAsT2f60CQq4UuhfNCNbIvJ6q3GQeJTFOSWQ2J7/WBQ1VNu07aJH2 5OjmIBiWPsq/m8X6UP0uFYBSZJaJ9rqEZEgSIbRR7gjjJBZrNSD0kiym/IPbg2kuDFpl uaFQ== X-Received: by 10.112.57.49 with SMTP id f17mr8081565lbq.26.1377106525776; Wed, 21 Aug 2013 10:35:25 -0700 (PDT) Received: from [192.168.1.200] ([188.134.10.29]) by mx.google.com with ESMTPSA id i9sm3298720laa.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 21 Aug 2013 10:35:24 -0700 (PDT) From: Sergey Arlashin Content-Type: multipart/alternative; boundary="Apple-Mail=_C1C6C171-1DB3-4E32-9F1A-ECA236C866A9" Subject: Standalone Hot Backups Message-Id: <1506B870-FE7D-4A13-B7BF-700F33BE9FC6@gmail.com> Date: Wed, 21 Aug 2013 21:35:23 +0400 To: "pgsql-admin@postgresql.org" Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --Apple-Mail=_C1C6C171-1DB3-4E32-9F1A-ECA236C866A9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi! I'm reading this article = http://www.postgresql.org/docs/current/static/continuous-archiving.htm In section 'Making a Base Backup Using the Low Level API' is said that = once one has WAL archiving set up it is ok to omit pg_xlog folder from = the backup dump: > "You can, however, omit from the backup dump the files within the = cluster's pg_xlog/ subdirectory. This slight adjustment is worthwhile = because it reduces the risk of mistakes when restoring. This is easy to = arrange if pg_xlog/ is a symbolic link pointing to someplace outside the = cluster directory, which is a common setup anyway for performance = reasons. You might also want to exclude postmaster.pid and = postmaster.opts, which record information about the running postmaster, = not about the postmaster which will eventually use this backup. (These = files can confuse pg_ctl.)" But in section related to making standalone hot backups there is no = information about it.=20 There is only the following set of commands: touch /var/lib/pgsql/backup_in_progress psql -c "select pg_start_backup('hot_backup');" tar -cf /var/lib/pgsql/backup.tar /var/lib/pgsql/data/ psql -c "select pg_stop_backup();" rm /var/lib/pgsql/backup_in_progress tar -rf /var/lib/pgsql/backup.tar /var/lib/pgsql/archive/ I only can see that the backup folder is being archived with pg_xlog.=20 So, the question is - is it ok to omit pg_xlog folder from backup dump = while making standalone hot backups or not ? -- best regards, Sergey= --Apple-Mail=_C1C6C171-1DB3-4E32-9F1A-ECA236C866A9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii http://www.postgresql.org/docs/current/static/continuous-archiving.h= tm

In section 'Making a Base Backup Using = the Low Level API' is said that once one has WAL archiving set up it is = ok to omit pg_xlog folder from the backup = dump:

"You can, however, omit from the backup dump the files within the = cluster's pg_xlog/ subdirectory. This slight adjustment is = worthwhile because it reduces the risk of mistakes when restoring. This = is easy to arrange if pg_xlog/ is = a symbolic link pointing to someplace outside the cluster directory, = which is a common setup anyway for performance reasons. You might also = want to exclude postmaster.pid and , which record information about the = running postmaster, not = about the postmasterpg_ctl

But in section = related to making standalone hot backups there is no information about = it. 

There is only the following set of = commands:

psql -c "select pg_start_backup('hot_backup');"
tar -cf = /var/lib/pgsql/backup.tar /var/lib/pgsql/data/
psql -c "select pg_stop_backup();"
rm /var/lib/pgsql/backup_in_progress
tar -rf = /var/lib/pgsql/backup.tar /var/lib/pgsql/archive/

I only can see that the backup folder is being archived = with pg_xlog. 

So, the question is - is it ok = to omit pg_xlog folder from backup dump while making standalone hot = backups or not = ?


--
best = regards,
Sergey
= --Apple-Mail=_C1C6C171-1DB3-4E32-9F1A-ECA236C866A9--