Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Xa5g6-0002Ao-GM for pgsql-admin@arkaria.postgresql.org; Fri, 03 Oct 2014 16:25:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Xa5g5-0004gx-ST for pgsql-admin@arkaria.postgresql.org; Fri, 03 Oct 2014 16:25:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Xa5g5-0004gr-61 for pgsql-admin@postgresql.org; Fri, 03 Oct 2014 16:25:57 +0000 Received: from mailout.easymail.ca ([64.68.201.169]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Xa5g0-0001qR-3b for pgsql-admin@postgresql.org; Fri, 03 Oct 2014 16:25:55 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 5E7CDDFE9; Fri, 3 Oct 2014 12:25:48 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca X-Spam-Flag: NO X-Spam-Score: -4.377 X-Spam-Level: X-Spam-Status: No, score=-4.377 required=5 tests=[ALL_TRUSTED=-1.8, AWL=0.022, BAYES_00=-2.599] Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJOzjkGmjNnj; Fri, 3 Oct 2014 12:25:47 -0400 (EDT) Received: from [192.168.2.16] (unknown [8.39.228.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id F0ECBDFD4; Fri, 3 Oct 2014 12:25:46 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Backup error From: Scott Ribe In-Reply-To: Date: Fri, 3 Oct 2014 10:25:44 -0600 Cc: Celso Vieira *EXTERN* , "pgsql-admin@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Albe Laurenz X-Mailer: Apple Mail (2.1878.6) X-Pg-Spam-Score: -1.9 (-) 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 On Oct 3, 2014, at 8:55 AM, Albe Laurenz wrote: > You have to wait until scp is finished before running pg_stop_backup. If, for performance reasons, you want to overlap backup & copy: 1) use rsync during the backup (repeat if it finishes before the backup) 2) after the backup has finished, but before running pg_stop_backup, run rs= ync again 3) pg_stop_backup There is a worry about a potential issue with granularity of timestamp on a= n open file finished rsyncing a split second before finished writing by bac= kup process, there's the -c option for the final rsync pass. But then it's = up to you to figure out whether it's actually worth having that extra read = of every byte of every file in order to get the head start. Depends on your= server I/O load, and relative speed of backup vs copy, and what your actua= l goal is. Personally, I do this not for recovery, but for snagging copies for testing= , and in that case I don't worry about the -c option. --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin