Re: RE : RE : PostgreSQL logical incremental backup for version 9.6 and above

You could also ask the question to AWS support. They are very good at
answering questions with steps and useful documentation.

On Thu, Nov 7, 2019, 12:56 PM PASCAL CROZET <
pascal(dot)crozet(at)qualis-consulting(dot)com> wrote:

> Ok all,
>
> I’ve to talk to my collegues working with AWS to provide a best answer.
>
> *_________________________________*
>
> Cordialement, *Pascal CROZET*
>
> *DBA - * <http://www.qualis-consulting.com>Qualis Consulting
> <http://www.qualis-consulting.com/>
>
> • www.qualis-consulting.com • 04 78 22 74 90
> • Le Bois des Côtes 1 – Bâtiment A
> • 300 Route Nationale 6 – 69760 LIMONEST
> *_________________________________*
>
>
>
> *De : *MichaelDBA <MichaelDBA(at)sqlexec(dot)com>
> *Envoyé le :*mercredi 6 novembre 2019 20:32
> *À : *girish R G peetle <giri(dot)anamika0(at)gmail(dot)com>
> *Cc : *PASCAL CROZET <pascal(dot)crozet(at)qualis-consulting(dot)com>; pgsql-admin
> <pgsql-admin(at)postgresql(dot)org>
> *Objet :*Re: RE : PostgreSQL logical incremental backup for version 9.6
> and above
>
>
> Hi,
> You can use pgbackrest to store WAL on AWS S3, but you need a binary
> backup from which to apply WAL to do PITR. pg_dump is not a binary backup.
> AWS RDS does not allow access to the underlying file system. So you cannot
> use pgbackrest to do backup or restore, or use the WAL you saved, let's say
> on S3, to do PITR.
>
> Regards,
> Michael Vitale
>
> girish R G peetle wrote on 11/6/2019 2:26 PM:
>
> Hi Pascal,
> Thanks for the suggestion. Looks like pgBackRest relies on WAL archive
> logs. But for Amazon RDS or Azure Database WAL logs are not accessible. We
> can only do pg_dump and logical replication.
> So pgBackRest won't work for my case.
>
> Thanks
> Girish
>
> On Wed, Nov 6, 2019 at 2:05 PM PASCAL CROZET <
> pascal(dot)crozet(at)qualis-consulting(dot)com> wrote:
>
>> Hi,
>>
>>
>>
>> I think you can user pgBackRest <https://pgbackrest.org/>
>>
>>
>>
>> *_________________________________*
>>
>> Cordialement, *Pascal CROZET*
>>
>> *DBA - * <http://www.qualis-consulting.com>Qualis Consulting
>> <http://www.qualis-consulting.com/>
>>
>> • www.qualis-consulting.com • 04 78 22 74 90
>> • Le Bois des Côtes 1 – Bâtiment A
>> • 300 Route Nationale 6 – 69760 LIMONEST
>> *_________________________________*
>>
>>
>>
>> *De : *girish R G peetle <giri(dot)anamika0(at)gmail(dot)com>
>> *Envoyé le :*mercredi 6 novembre 2019 18:03
>> *À : *pgsql-admin <pgsql-admin(at)postgresql(dot)org>
>> *Objet :*PostgreSQL logical incremental backup for version 9.6 and above
>>
>>
>> Hi,
>> I've a requirement to backup incremental data from PostgreSQL database
>> server which are hosted as 'database as a service' like 'Amazon RDS' ,
>> Azure Database etc.
>>
>> Full dump can be taken using pg_dump. But is there is a way to capture
>> incremental changes to the database ? I read about logical replication
>> slots which can be created for each database to capture incremental
>> changes.
>> But how do we know from where we should backup the SQL statements (as we
>> need need skip those statements already backed up by pg_dump).
>>
>> I thinking of following steps.
>> Step 1: Create logical replication slot
>> Step 2: Run pg_dump ( for full load ).
>> Step 3: Capture the changes since last pg_dump using replication slot -
>> How to know this information ?
>>
>> Thanks in advance for any advise.
>>
>> Thanks
>> Girish
>>
>
>