Hello Laurenz
As per my understanding coming to a proper conclusion wrt RPO with export operation is challenging. Eg., the export started at x and ended at z, the time stamp here for many data sets is different. Moreover, I do not think there is an incremental way available for export, correct?
Please correct me if my understanding is wrong.
Although I do agree the primary choice of backup to be storage based, we wanted to have export backups as well as a secondary.
Concerning the impact taking export on read only.. Would you think we may run into recovery issues on the replica side or anything that would prevent the operation from being successful?
Regards
Siraj
On Thu, Mar 20, 2025 at 5:29 PM Laurenz Albe <laurenz.albe@xxxxxxxxxxx> wrote:
On Thu, 2025-03-20 at 17:22 +0530, Siraj G wrote:
> I have a DB with 1TB in size serving needs of one of our critical
> applications. I have a requirement to take export of the DB on a
> daily basis, but want to carry out this operation in read replica.
> The postgresql version is: 16.6
>
> What would be the RPO of such backup?
Depends on the speed of disk and network and on what an RPO is.
> What would be the impact on the READ REPLICA with a long running
> export operation?
Potentially severe.
You could look into storage technologies that allow you to take
a snapshot and clone it.
Yours,
Laurenz Albe
