On Thu, Dec 14, 2017 at 4:29 PM, PropAAS DBA <dba@xxxxxxxxxxx> wrote:
However restoring the snapshot with veeam will restore the db to a running/online state, which means we cannot force it to go back into recovery mode yes?
On 12/14/2017 01:19 AM, Laurenz Albe wrote:
PropAAS DBA wrote:
we have a client using veeam to do vmware snapshots of the db servers,It is fairly simple.
unfortunately as far as I can tell any restore of a veeam snapshot also
restores the state, which means the db gets restored in an online state.
As far as I know, once the db is online we cannot force it back into
recovery mode to do a PITR recovery, correct?
Anyone know of a way to do PITR recoveries with veeam?
Before the snapshot, run
SELECT pg_start_backup('label of your choice', TRUE);
After the snapshot, run
SELECT pg_stop_backup();
Yours,
Laurenz Albe
If your snapshots include the memory/cpu state, then you cannot use them for point in time recovery. It only works if what you snapshot is the disk.
If the snapshots include memory/cpu state they should be usable without the WAL. *should* being the operative word. But not for PITR.
I don't know veeam specifically, though, so I don't know how it works there. Unless they specifically document support for it, I wouldn't use it for PITR under any conditions.
