Re: Netapp SnapCenter - Mailing list pgsql-general

From Wolff, Ken L
Subject Re: Netapp SnapCenter
Date
Msg-id 9530455b85e640deb1dbe74d6a5a2a74@lmco.com
Whole thread Raw
In response to Netapp SnapCenter  (Paul Förster <paul.foerster@gmail.com>)
Responses Re: Netapp SnapCenter  (Paul Förster <paul.foerster@gmail.com>)
List pgsql-general
So apologies if this is a stupid question but there's obviously been a lot of discussion on this issue.  Was a
consensusever reached on the following? 

If a Postgres database (both data and WAL) is located on one NetApp volume, meaning a snapshot should capture
everythingat exactly the same time with the required atomicity, do we still need to put the database into backup mode
beforehand(and take it out afterwards)?  If we don't put Postgres into backup mode first, will we still be able to use
theWALs to roll transactions forward or would we be limited to only the point-in-time at which that snapshot was taken? 

Thanks much.

Ken

-----Original Message-----
From: Stephen Frost <sfrost@snowman.net>
Sent: Monday, June 22, 2020 7:06 AM
To: Paul Förster <paul.foerster@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>; Wolff, Ken L (US) <ken.l.wolff@lmco.com>; pgsql-general
<pgsql-general@postgresql.org>
Subject: EXTERNAL: Re: Netapp SnapCenter

Greetings,

* Paul Förster (paul.foerster@gmail.com) wrote:
> > On 22. Jun, 2020, at 13:08, Magnus Hagander <magnus@hagander.net> wrote:
> > It does not work off *that* base backup. But if you start from the *prior* be backup (one that did complete with a
successfulpg_stop_backup) then you can still use the archived wal to recover to any point in time.  
>
> ok, that's clear now. Thank you very much.

Right, and tools like pgbackrest will figure this kind of thing out for you too- just give it the time you want to
restoreto and it'll figure out the right backup to use. 

Thanks,

Stephen



pgsql-general by date:

Previous
From: "Peter J. Holzer"
Date:
Subject: Re: ERROR: invalid memory alloc request size 18446744073709551613
Next
From: Michel Pelletier
Date:
Subject: Re: Hiding a GUC from SQL