From: | Johann Spies <johann(dot)spies(at)gmail(dot)com> |
---|---|
To: | Eduardo Morras <emorrasg(at)yahoo(dot)es> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, sthomas(at)optionshouse(dot)com |
Subject: | Re: Backup advice |
Date: | 2013-04-10 07:58:05 |
Message-ID: | CAGZ55DTpdsJRDF73XDwJ801pko02USoOi3e3x-14PmR4KmBXPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks everybody for your valuable comments.
I can specify how many versions of the files should be kept on Tivoli.
The database will regularly get new data and there is a continuous process
of data cleaning. It is a database mainly for research purposes and a few
researchers are using it.
I will explore the options mentioned. After the first read it looks like
continuing pg_dump is not a bad idea - maybe with some optimization (like
using diff's).
Regards
Johann
On 9 April 2013 12:05, Eduardo Morras <emorrasg(at)yahoo(dot)es> wrote:
> On Mon, 8 Apr 2013 10:40:16 -0500
> Shaun Thomas <sthomas(at)optionshouse(dot)com> wrote:
>
> >
> > Anyone else?
> >
>
> If his db has low inserts/updates/deletes he can use diff between pg_dumps
> (with default -Fp) before compressing.
>
> --- ---
> Eduardo Morras <emorrasg(at)yahoo(dot)es>
>
>
> --
> 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
>
--
Because experiencing your loyal love is better than life itself,
my lips will praise you. (Psalm 63:3)
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriele Bartolini | 2013-04-10 08:11:21 | Re: Backup advice |
Previous Message | Albe Laurenz | 2013-04-10 07:36:59 | Re: What is pg backend using memory for? |