Re: Postgres backup solution

Your message is not diplaying. At least not for me. I guess that my reader
does not understand the "smime.p7m" file, which shows as an attachment. For
others, his question is:

=== original question from Lawrence Cohan ===

Yes, this is what I intended to ask:

What would be a recommended solution for backing up a very large Postgres
(~13TeraBytes) database in order to prevent from data deletion/corruption.
Current setup is only to backup/restore to a standby read-only Postgres
server
via AWS S3 using wal-e however this does not offer the comfort of keeping a
full backup available in case we need to restore some deleted or corrupted
data.

Thanks,

Lawrence Cohan

===

On Tue, Mar 14, 2017 at 2:57 PM, Lawrence Cohan <LCohan(at)web(dot)com> wrote:

>
> ________________________________
>
> Attention:
> The information contained in this message and or attachments is intended
> only for the person or entity to which it is addressed and may contain
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the sender and
> delete the material from any system and destroy any copies.
>
>
> ---------- Forwarded message ----------
> From: Lawrence Cohan <LCohan(at)web(dot)com>
> To: John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <
> pgsql-general(at)postgresql(dot)org>
> Cc:
> Bcc:
> Date: Tue, 14 Mar 2017 15:57:39 -0400
> Subject: RE: [GENERAL] Postgres backup solution
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
>

--
"Irrigation of the land with seawater desalinated by fusion power is
ancient. It's called 'rain'." -- Michael McClary, in alt.fusion

Maranatha! <><
John McKown