public inbox for [email protected]
help / color / mirror / Atom feedBackup_Long Running
5+ messages / 4 participants
[nested] [flat]
* Backup_Long Running
@ 2024-04-24 07:03 jaya kumar <[email protected]>
2024-04-24 09:20 ` Re: Backup_Long Running Vijaykumar Jain <[email protected]>
2024-04-24 15:10 ` Re: Backup_Long Running Adrian Klaver <[email protected]>
0 siblings, 2 replies; 5+ messages in thread
From: jaya kumar @ 2024-04-24 07:03 UTC (permalink / raw)
To: pgsql-general
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.
Backup File size=613G
Backup Running Duration: 8 Hours
--
Thanks & Regards,
Jayakumar.S
+91-9840864439.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Backup_Long Running
2024-04-24 07:03 Backup_Long Running jaya kumar <[email protected]>
@ 2024-04-24 09:20 ` Vijaykumar Jain <[email protected]>
2024-04-24 12:30 ` Re: Backup_Long Running jaya kumar <[email protected]>
1 sibling, 1 reply; 5+ messages in thread
From: Vijaykumar Jain @ 2024-04-24 09:20 UTC (permalink / raw)
To: jaya kumar <[email protected]>; +Cc: pgsql-general
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.
>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Backup_Long Running
2024-04-24 07:03 Backup_Long Running jaya kumar <[email protected]>
2024-04-24 09:20 ` Re: Backup_Long Running Vijaykumar Jain <[email protected]>
@ 2024-04-24 12:30 ` jaya kumar <[email protected]>
2024-04-24 12:32 ` Re: Backup_Long Running Ron Johnson <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: jaya kumar @ 2024-04-24 12:30 UTC (permalink / raw)
To: Vijaykumar Jain <[email protected]>; +Cc: pgsql-general
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Backup_Long Running
2024-04-24 07:03 Backup_Long Running jaya kumar <[email protected]>
2024-04-24 09:20 ` Re: Backup_Long Running Vijaykumar Jain <[email protected]>
2024-04-24 12:30 ` Re: Backup_Long Running jaya kumar <[email protected]>
@ 2024-04-24 12:32 ` Ron Johnson <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Ron Johnson @ 2024-04-24 12:32 UTC (permalink / raw)
To: pgsql-general
PgBackRest is in the PGDG repositories (RHEL & Debian).
The documentation is thorough, and discoverable via Google,
On Wed, Apr 24, 2024 at 8:30 AM jaya kumar <[email protected]> wrote:
> 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.
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Backup_Long Running
2024-04-24 07:03 Backup_Long Running jaya kumar <[email protected]>
@ 2024-04-24 15:10 ` Adrian Klaver <[email protected]>
1 sibling, 0 replies; 5+ messages in thread
From: Adrian Klaver @ 2024-04-24 15:10 UTC (permalink / raw)
To: jaya kumar <[email protected]>; pgsql-general
On 4/24/24 00:03, jaya kumar wrote:
> Hi Team,
>
> Production database Backup is running very long hours. Any option to
> reduce backup time? Kindly advise me.
Hardware specifications?
Network specifications?
The actual pg_basebackup command used?
Server(s) user load?
>
> DB size: 793 GB
>
> We are taking pg_basebackup backup.
>
> Backup File size=613G
>
> Backup Running Duration: 8 Hours
>
>
> --
> Thanks & Regards,
> Jayakumar.S
> +91-9840864439.
--
Adrian Klaver
[email protected]
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2024-04-24 15:10 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-04-24 07:03 Backup_Long Running jaya kumar <[email protected]>
2024-04-24 09:20 ` Vijaykumar Jain <[email protected]>
2024-04-24 12:30 ` jaya kumar <[email protected]>
2024-04-24 12:32 ` Ron Johnson <[email protected]>
2024-04-24 15:10 ` Adrian Klaver <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox