On Thu, Aug 29, 2024 at 6:54 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:On Thu, Aug 29, 2024 at 2:21 AM KK CHN <kkchn.in@gmail.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 resumeAny suggestions much appreciatedBoost 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 ?
On Thu, Aug 29, 2024 at 2:21 AM KK CHN <kkchn.in@gmail.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 resumeAny suggestions much appreciatedBoost your process-max as high as you are able to speed up your backup time.
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 ?
Any suggestions much appreciated
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 ?
pgsql-general by date:
Соглашаюсь с условиями обработки персональных данных
