[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: pg_update to a new machine?
From:       Ron Johnson <ron.l.johnson () cox ! net>
Date:       2018-02-25 0:48:11
Message-ID: ca1b40f7-b209-8aae-3c10-73be3a811863 () cox ! net
[Download RAW message or body]

On 02/24/2018 06:40 PM, Stephen Frost wrote:
> Ron,
>
> * Ron Johnson (ron.l.johnson@cox.net) wrote:
>> On 02/24/2018 03:10 PM, Stephen Frost wrote:
>> [snip]
>>>> To set up log shipping on 8.4, I do this, which works well:
>>>>
>>>> select pg_start_backup('some_meaningful_tag');
>>>> nohup rsync -avz /var/lib/pgsql/data/* postgres@${DESTIP}:/var/lib/pgsql/data/ &
>>>> select pg_stop_backup();
>>> That's not log shipping, for log shipping you need to specify an
>>> archive_command and actually capture all of the WAL generated, or, at a
>>> minimum, the WAL generated between the start and stop backup calls.
>> That's steps #8, 9 and 10 (in our checklist) of setting up log shipping.
>> Step #4 is configuring the archive_* statements in postgresql.conf.
> I would still recommend you use a tool developed specifically for taking
> proper PG backups which validates that all WAL generated during a backup
> is properly archived, such as pgBackRest, which also makes sure to sync
> all the data out to persistent storage and can also operate in parallel
> and perform incremental restores.

OK.  I'll try to get it installed.  (Lots of paperwork, etc.)


-- 
Angular momentum makes the world go 'round.


[prev in list] [next in list] [prev in thread] [next in thread]