From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Echlin, Jamie (KFIA 611) *EXTERN*" <jamie(dot)echlin(at)credit-suisse(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: need a hand with my backup strategy please... |
Date: | 2013-09-17 13:22:01 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17C216E0@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jamie Echlin wrote:
> I was planning to rely on the disk backup (of the base backup) if I wanted to restore to a version
> before the last on disk base backup. But your point about redundancy is good... I think I will keep
> two base backups, and do a base backup every day. Over the network this takes 5-10 mins or so, so not
> a big deal.
>
> I'll retain wals for 48 hours. Having to go to a PIT before the last hour or so would be a major
> undertaking anyway.
I have seen cases where a software bug in the application gradually
caused data in the database to be changed. It took a while to notice that.
In such a case you want to have a backup from a month ago or more so that
you can extract the data as they were back then and try to repair as much
as possible.
Also, what if a problem was introduced right before the weekend and noticed
immediately afterwards? That might be more than 48 hours ago.
There are other scenarios where a backup from longer ago would really help.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Bret Stern | 2013-09-17 14:06:14 | Re: Using ODBC and VBA to pull data from a large object |
Previous Message | Merlin Moncure | 2013-09-17 13:11:38 | Re: best practice for || set of rows --> function --> set of rows |