public inbox for [email protected]help / color / mirror / Atom feed
Re: PgBackRest Full backup and N/W reliability 3+ messages / 3 participants [nested] [flat]
* Re: PgBackRest Full backup and N/W reliability @ 2024-08-29 13:24 Greg Sabino Mullane <[email protected]> 2024-08-29 16:07 ` Re: PgBackRest Full backup and N/W reliability KK CHN <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Greg Sabino Mullane @ 2024-08-29 13:24 UTC (permalink / raw) To: KK CHN <[email protected]>; +Cc: pgsql-general On Thu, Aug 29, 2024 at 2:21 AM KK CHN <[email protected]> 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. Cheers, Greg ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PgBackRest Full backup and N/W reliability 2024-08-29 13:24 Re: PgBackRest Full backup and N/W reliability Greg Sabino Mullane <[email protected]> @ 2024-08-29 16:07 ` KK CHN <[email protected]> 2024-08-29 18:10 ` Re: PgBackRest Full backup and N/W reliability Ron Johnson <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: KK CHN @ 2024-08-29 16:07 UTC (permalink / raw) To: Greg Sabino Mullane <[email protected]>; +Cc: pgsql-general On Thu, Aug 29, 2024 at 6:54 PM Greg Sabino Mullane <[email protected]> wrote: > On Thu, Aug 29, 2024 at 2:21 AM KK CHN <[email protected]> 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 > > > ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PgBackRest Full backup and N/W reliability 2024-08-29 13:24 Re: PgBackRest Full backup and N/W reliability Greg Sabino Mullane <[email protected]> 2024-08-29 16:07 ` Re: PgBackRest Full backup and N/W reliability KK CHN <[email protected]> @ 2024-08-29 18:10 ` Ron Johnson <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Ron Johnson @ 2024-08-29 18:10 UTC (permalink / raw) To: pgsql-general On Thu, Aug 29, 2024 at 12:08 PM KK CHN <[email protected]> wrote: > > On Thu, Aug 29, 2024 at 6:54 PM Greg Sabino Mullane <[email protected]> > wrote: > >> On Thu, Aug 29, 2024 at 2:21 AM KK CHN <[email protected]> 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 ? > We can't answer that. It depends on what else your PG and PgBackRest servers are doing when "pgbackrest backup" runs. > 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 ? > "pgbackrest backup" reads the config file when it starts. > Is there a limit for proces max. setting ? > I think you need managed DBA services. -- Death to America, and butter sauce. Iraq lobster! ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2024-08-29 18:10 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-08-29 13:24 Re: PgBackRest Full backup and N/W reliability Greg Sabino Mullane <[email protected]> 2024-08-29 16:07 ` KK CHN <[email protected]> 2024-08-29 18:10 ` Ron Johnson <[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