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 12:47:59 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17C2164A@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jamie Echlin wrote:
> What I'm trying to say is that I configured it to keep (60/5) * 24 segments plus a few spare, because
> I am switching xlog every 5 mins. But if there is heavy load then they will be generated more often
> than every 5 mins, so that number won't be enough.
You should delete archived WAL files by age, that way you shouldn't
have a problem.
> But I think it's a moot point because they seem to be useless unless you have all of them up to the
> last base backup. Which to me indicates I need to do a base backup every day...?
You just need any base backup plus *all* archived WALs
since the beginning of the backup.
Of course you want a fairly recent backup, otherwise
applying the WAL files can take very long.
It is a good idea to keep more than one base backup in case
something goes wrong (bad backup).
Another reason to keep older backups is that you may want to recover
to a point in time that lies further in the past, e.g. if it takes some
time to discover a problem that requires recovery (corruption, ...).
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Echlin, Jamie (KFIA 611) | 2013-09-17 12:54:06 | Re: need a hand with my backup strategy please... |
Previous Message | tdev457 | 2013-09-17 12:46:06 | Number of WAL segment |