From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Marcin Giedz <marcin.giedz@eulerhermes.pl>
Cc: pgsql-admin@postgresql.org
Subject: Re: Backup issue
Date: Mon, 19 Sep 2005 11:52:44 -0500
Message-ID: <1127148764.30120.102.camel@state.g2switchworks.com> (raw)
In-Reply-To: <432BCAA0.6020902@eulerhermes.pl>
References: <432BCAA0.6020902@eulerhermes.pl>
On Sat, 2005-09-17 at 02:49, Marcin Giedz wrote:
> Hello...
>
> This is what I have now: postgresql 8.0.1 - database weights about 60GB
> and increases about 2GB per week. Nowadays I do backup every day -
> according to simple procedure (pg_start_backup:rsync
> data:pg_stop_backup:save wals produced during backup). On 1Gb internal
> network it usually takes me about 1h to perform this procedure.
>
> But what if my database has ~200GB and more (I know this is a future
> :D)? From my point of view it won't be good idea to copy entire database
> to backup array. I would like to here opinions about this case - what do
> you propose? Maybe some of you already do something like this?
I'd look at using PITR replication, with a monthly or so fresh, whole
backup instead of a whole backup every day.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, marcin.giedz@eulerhermes.pl
Subject: Re: Backup issue
In-Reply-To: <1127148764.30120.102.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox