public inbox for [email protected]  

help / color / mirror / Atom feed

From: jaya kumar <[email protected]>
To: Vijaykumar Jain <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Backup_Long Running
Date: Wed, 24 Apr 2024 18:00:03 +0530
Message-ID: <CACd4L3v0QLJR_rho_p7Qne3a=xgOf0XeCBqTJZFP0_NKn_S1Uw@mail.gmail.com> (raw)
In-Reply-To: <CAM+6J97kZGKDgzvUE26bzoOPm0++tXO0P-oqr_9pTbNFbdinHw@mail.gmail.com>
References: <CACd4L3u23i3YX6rATRBH1LeaDNnNrWRuuGyW-hVoDeh3F9i7vA@mail.gmail.com>
	<CAM+6J97kZGKDgzvUE26bzoOPm0++tXO0P-oqr_9pTbNFbdinHw@mail.gmail.com>

Thanks for your update. Can you have any link or document to configure L0 &
L1 backup using pgbackrest tool. Also share the pgbackrest installation
method.

On Wed, Apr 24, 2024 at 2:50 PM Vijaykumar Jain <
[email protected]> wrote:

>
> On Wed, Apr 24, 2024, 12:33 PM jaya kumar <[email protected]> wrote:
>
>> Hi Team,
>>
>>
>>
>> Production database Backup is running very long hours. Any option to
>> reduce backup time? Kindly advise me.
>>
>>
>>
>> DB size: 793 GB
>>
>>
>>
>> We are taking pg_basebackup backup.
>>
>>
> do you see network saturation, io saturation ?
> generally faster hardware i.e striped and or nvme disks along with a
> robust network link and capacity should help get the backup done quickly.
> where are you taking the backup from? is the server busy doing other work
> or it is a dedicated machine for backups ?
> basically monitor for resource saturation, if all looks good, we could
> take basebackup of a 10tb db in 8 hours, and in another case on a slow
> remote storage, backup of 2tb took 1 day.
>
> now, pgbackrest can speedup backup processes by spawning more workers for
> archiving and stuff. we have taken backup on nvme disks striped of 28tb in
> 3 hours, bare metals servers with powerful cpu.
>
> so , it's hardware .... else switch to pgbackrest which can take
> incremental/differential/full backups.
> there are other tools too, I used only these two.
>
>>
>>

-- 
Thanks & Regards,
Jayakumar.S
+91-9840864439.

view thread (5+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Backup_Long Running
  In-Reply-To: <CACd4L3v0QLJR_rho_p7Qne3a=xgOf0XeCBqTJZFP0_NKn_S1Uw@mail.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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox