From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Albe Laurenz <laurenz.albe@wien.gv.at>
Cc: Celso Vieira *EXTERN* <sabd.secinfo@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Backup error
Date: Fri, 3 Oct 2014 10:25:44 -0600
Message-ID: <D0E44AD2-0312-41C8-AEB4-72610EDCC79C@elevated-dev.com> (raw)
In-Reply-To: <A737B7A37273E048B164557ADEF4A58B17D5581B@ntex2010i.host.magwien.gv.at>
References: <CANR-yjpTxEdHpqT4nUpfJERH4sjJuaqcGevfEaw57KifuQo9ug@mail.gmail.com>
<A737B7A37273E048B164557ADEF4A58B17D556B9@ntex2010i.host.magwien.gv.at>
<CAGDYbUPE1e2GPecLwf-+QN3ef5S2hNObGpF_JTSZx9=hC0qLPQ@mail.gmail.com>
<CANR-yjpE0yQTuaneNJV4-i4d+zrDRpUWwu87Lhx5UG1vJZv5xQ@mail.gmail.com>
<A737B7A37273E048B164557ADEF4A58B17D5581B@ntex2010i.host.magwien.gv.at>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Oct 3, 2014, at 8:55 AM, Albe Laurenz <laurenz.albe@wien.gv.at> 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 rsync again
3) pg_stop_backup
There is a worry about a potential issue with granularity of timestamp on an open file finished rsyncing a split second before finished writing by backup 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 actual 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.
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: scott_ribe@elevated-dev.com, laurenz.albe@wien.gv.at, sabd.secinfo@gmail.com
Subject: Re: Backup error
In-Reply-To: <D0E44AD2-0312-41C8-AEB4-72610EDCC79C@elevated-dev.com>
* 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