Re: [GENERAL] Google Cloud Platform, snapshots and WAL - Mailing list pgsql-general

From Ben Chobot
Subject Re: [GENERAL] Google Cloud Platform, snapshots and WAL
Date
Msg-id F78A1CFE-BCE4-4BBB-9B44-9D491010B280@silentmedia.com
Whole thread Raw
In response to [GENERAL] Google Cloud Platform, snapshots and WAL  (Moreno Andreo <moreno.andreo@evolu-s.it>)
Responses Re: [GENERAL] Google Cloud Platform, snapshots and WAL
List pgsql-general

On Mar 20, 2017, at 6:31 AM, Moreno Andreo <moreno.andreo@evolu-s.it> wrote:

Hi everyone,

   I have my PostgreSQL 9.5 server running on a VM instance on Google Compute Engine (Google Cloud Platform) on Debian Jessie (8.3), and I have another dedicated VM instance that, every night at 3.00, takes a snapshot of the whole disk, without stopping the PG instance itself.
Snapshots are stored and kept by Google in an incremental way, and we keep the last 2 weeks of history.
The question is: Keeping all two weeks worth of pg_xlog files, I don't think I still need a periodic pg_basebackup to perform PITR, do I?

You need a base backup to apply your wals to. So long as you have one from after the start of your wal stream, you should be good for PITR. That said, replaying 2 weeks of wal files can take a long time. For that reason alone, it might well make sense to have more than a single basebackup snapshot.

Also, I cannot stress enough how important it is to actually test your recovery strategy. Few things are worse than assuming you can recover only to find out when you need to that you cannot. Do not let https://about.gitlab.com/2017/02/10/postmortem-of-database-outage-of-january-31/ happen to you.

pgsql-general by date:

Previous
From: George Neuner
Date:
Subject: Re: [GENERAL] Postgres goes to auto recovery mode after system restart(check this draft)
Next
From: ibeq GmbH
Date:
Subject: [GENERAL] Why is this functional index not used?