Re: pg15 and VM snapshots with pg_backup_start - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: pg15 and VM snapshots with pg_backup_start
Date
Msg-id 99815bc4cd2622115ea417f6f1e3ceebf8a5247e.camel@cybertec.at
Whole thread Raw
In response to pg15 and VM snapshots with pg_backup_start  (oernii+pg@axonpro.sk)
Responses Re: pg15 and VM snapshots with pg_backup_start  (Stephen Frost <sfrost@snowman.net>)
List pgsql-admin
On Thu, 2023-03-30 at 11:50 +0200, oernii+pg@axonpro.sk wrote:
> Hi, we run a lot of PG14 and lower. We do VM snapshots, which we backup.
> Before the snapshot we run a quiesce script which also runs pg_start_backup().
> After a few seconds the snapshot if finished and we call pg_stop_backup.
> This is working file for us, but pg15 removed this function and replaced it
> with pg_backup_start(), which however requires the session to be open, otherwise we get:
>     WARNING:  aborting backup due to backend exiting before pg_backup_stop was called
>
> For pg15 do I need to keep the session open, will the snapshot contain uncorruped data?

If the snapshot is atomic, that is, represents a state that the file system had
at sume point in time, PostgreSQL can always use it for recovery.

Otherwise, you cannot use this backup, because you only get "backup_label" from
"pg_backup_stop()", and without "backup_label", you cannot recover the backup.

In the latter case, you may find this useful:
https://github.com/cybertec-postgresql/safe-backup

Yours,
Laurenz Albe



pgsql-admin by date:

Previous
From: oernii+pg@axonpro.sk
Date:
Subject: pg15 and VM snapshots with pg_backup_start
Next
From: Stephen Frost
Date:
Subject: Re: pg15 and VM snapshots with pg_backup_start