Message-ID: <3DA2E5F8.EA496ADD@postgresql.org>
Date: Wed, 09 Oct 2002 00:04:40 +1000
From: Justin Clift <justin@postgresql.org>
MIME-Version: 1.0
To: Erwan DUROSELLE <EDuroselle@seafrance.fr>
Cc: itvthor@sdf.lonestar.org, kleptog@svana.org, pgsql-general@postgresql.org
Subject: Re: Hot Backup
References: <f83feacee1d351df62199be3df8ea6af3da2cdd3@>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi Erwan,

Erwan DUROSELLE wrote:
<snip>
> As someone said, Replication may be a way to reduce the risks.

Yes, it can, but it all depends on how much the data is worth, what kind
of load happens, etc.

Something as simple as a master->slave replication setup will do,
because the master would generally be the beefy box doing processing,
and the slave database server only receives changes, etc.

Useful for lots of circumstances, although not the only solution.

:-)

Regards and best wishes,

Justin Clift

 
> E.D.
> 
> -------------------------------------------------------------------------------
> Erwan DUROSELLE    //    SEAFRANCE DSI
> Responsable Bases de Données  //  Databases Manager
> Tel: +33 (0)1 55 31 59 70    //    Fax: +33 (0)1 55 31 85 28
> email: eduroselle@seafrance.fr
> -------------------------------------------------------------------------------

-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi