From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: postgres large database backup
Date: Wed, 30 Nov 2022 13:06:53 -0600
Message-ID: <bc763ac9-e11b-051c-cfb7-8de60666c08b@gmail.com> (raw)
In-Reply-To: <CAM+6J96m9rM+jXw8n_-_ZyiUDXOQ555XH0UOJEt6TLFYH2zLDA@mail.gmail.com>
References: <CA+ONtZ7CdiJ2X8x_8sPHR+tz-vv7mR1uoDzLia3fzWVZA9k0JQ@mail.gmail.com>
<CAM+6J96m9rM+jXw8n_-_ZyiUDXOQ555XH0UOJEt6TLFYH2zLDA@mail.gmail.com>
On 11/30/22 11:41, Vijaykumar Jain wrote:
>
> On Wed, Nov 30, 2022, 9:10 PM Atul Kumar <akumar14871@gmail.com> wrote:
>
> Hi,
>
> I have a 10TB database running on postgres 11 version running on
> centos 7 "on premises", I need to schedule the backup of this database
> in a faster way.
>
> The scheduled backup will be used for PITR purposes.
>
> So please let me know how I should do it in a quicker backup for my
> 10TB database ? Is there any tool to take backups and subsequently
> incremental backups in a faster way and restore it for PITR in a
> faster way when required.
>
> What should be the exact approach for scheduling such backups so that
> it can be restored in a faster way ?
>
>
>
> We had a 96 cpu, 385gb ram, nvme storage and 10g network baremetal server.
> We used pgbackrest for full backup.
> It supports pitr and differential backup.
>
> 28tb db took 2.5 hours for backup on remote storage, and restore from the
> remote storage took 3.5 hours when immediately restored (a lot of time is
> later due to wal replay to catch up)
Another vote for pgbackrest. It supports AES encryption, and multiple forms
of compression.
--
Angular momentum makes the world go 'round.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: postgres large database backup
In-Reply-To: <bc763ac9-e11b-051c-cfb7-8de60666c08b@gmail.com>
References: <CA+ONtZ7CdiJ2X8x_8sPHR+tz-vv7mR1uoDzLia3fzWVZA9k0JQ@mail.gmail.com> <CAM+6J96m9rM+jXw8n_-_ZyiUDXOQ555XH0UOJEt6TLFYH2zLDA@mail.gmail.com> <bc763ac9-e11b-051c-cfb7-8de60666c08b@gmail.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