From: Karl Denninger <karl@denninger.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Incremental Postgres database backup
Date: Mon, 7 Mar 2022 09:30:31 -0500
Message-ID: <9962e5ba-a910-0226-56ed-245fcfc0ac3f@denninger.net> (raw)
In-Reply-To: <6405c132-283e-98b7-5447-b68eee447cf0@gmail.com>
References: <CAK_Ha4y5d8bRb4QwaaQh3ayB9bcjVE665dA4jWjnv_zPOu=6Ow@mail.gmail.com>
<6405c132-283e-98b7-5447-b68eee447cf0@gmail.com>
On 3/7/2022 09:03, Ron wrote:
> On 3/6/22 23:53, Firthouse banu wrote:
>> Hello Team,
>>
>> Needed an expert advice.
>> Can you guys suggest me to a open source tool which can be used to
>> take incremental backup of individual Postgres databases…
>>
>> We have very large databases whose sizes are again TBs when we do
>> pg_dump or pg_dump all its taking days to complete backups ..
>
> We use PgBackRest, and are very pleased with it.
>
Ditto here. It works very well and has the advantage of being able to
produce an immediately-startable copy of the master.
One caution; you have to pay attention when doing upgrades, even of
minor versions.
The other obvious option is online replication.
--
Karl Denninger
karl@denninger.net
/The Market Ticker/
/[S/MIME encrypted email preferred]/
Attachments:
smime.p7s (application/pkcs7-signature, 4.8K) download
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: karl@denninger.net, pgsql-admin@lists.postgresql.org
Subject: Re: Incremental Postgres database backup
In-Reply-To: <9962e5ba-a910-0226-56ed-245fcfc0ac3f@denninger.net>
* 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