Re: PgBackRest Full backup and N/W reliability

From: KK CHN <kkchn(dot)in(at)gmail(dot)com>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: PgBackRest Full backup and N/W reliability
Date: 2024-08-29 16:07:39
Message-ID: CAKgGyB-6_d+ch69jFPd6TaBnHgV5XmpHjP4AfkuRbk8H8EKssA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Aug 29, 2024 at 6:54 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:

> On Thu, Aug 29, 2024 at 2:21 AM KK CHN <kkchn(dot)in(at)gmail(dot)com> wrote:
>
>> I am doing a full backup using PgBackRest from a production server to
>> Reposerver.
>>
> ...
>
>> If so, does the backup process start again from scratch ? or it
>> resumes from where the backup process is stopped ?
>>
>
> It resumes. You will see a message like this:
>
> WARN: resumable backup 20240829-091727F of same type exists -- invalid
> files will be removed then the backup will resume
>
> Any suggestions much appreciated
>>
>
> Boost your process-max as high as you are able to speed up your backup
> time.
>
>
what will be the ideal process-max number to use ?

Once I update the process-max param in pgbackrest.conf , do I need to
stop and start the pgback rest ?

Or just editing the pgbackrest.conf on the fly will reflect the increased
process-max numbers advantage ?

Is there a limit for proces max. setting ?

> Cheers,
> Greg
>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message KK CHN 2024-08-29 16:42:37 PgBackRest Ideal N/W need to provisioned ?
Previous Message Ron Johnson 2024-08-29 14:47:23 Re: PgBackRest client_loop: send disconnect: Connection reset