Re: missing support for Microsoft VSS Writer - Mailing list pgsql-hackers

From Juan José Santamaría Flecha
Subject Re: missing support for Microsoft VSS Writer
Date
Msg-id CAC+AXB3n2mgP+CYyX2YgubvRakO5S+cWOvfTA+uRHt9JrYp=rw@mail.gmail.com
Whole thread Raw
In response to missing support for Microsoft VSS Writer  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers

On Fri, Jun 19, 2020 at 7:20 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:
some czech user reported a broken database when he used a repair point on Microsoft Windows. 

The reply from Microsoft was, so it is not a Microsoft issue, but Postgres issue, because Postgres doesn't handle VSS process correctly, and then restore point can restore some parts of Postgres's data too.


That is pretty much trying to do file system level backup [1], and the same caveats apply. Most likely, anything but a repair point with a shutdown server will result in a broken database when restored.

In order to get a consistent copy there has to be a specific Postgres Writer [2]. There are some samples on how to use the interface with the Volume Shadow Copy Service [3], but I do not think there is an interface to a file-system consistent snapshot in any other system.


Regards,

Juan José Santamaría Flecha

pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: Parallel copy
Next
From: Michael Paquier
Date:
Subject: Re: min_safe_lsn column in pg_replication_slots view