Message-ID: <5bb1a62ac2bb9add42b96b508829526d.squirrel@zenmail.co.za>
In-Reply-To: <4860970E.9070305@careerjunction.co.za>
References: <4860970E.9070305@careerjunction.co.za>
Date: Tue, 24 Jun 2008 08:53:28 +0200 (SAST)
Subject: Re: replication
From: "Henry - Zen Search SA" <henry@zen.co.za>
To: "Adrian Moisey" <adrian@careerjunction.co.za>
Cc: pgsql-general@postgresql.org
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

On Tue, June 24, 2008 8:41 am, Adrian Moisey wrote:
> Hi
>
> We have a 100GB database (16GB dumped) running on 8.2.
>
> Since the bandwidth in South Africa isn't that freely available it is
> difficult for us to get a new copy of out DB in our office (our fastest
> link in the office is 4Mbps).
>
> What can you recommend for me to get an up to date copy of my DB in the
> office with as little transfer as possible.
>
> A few ideas I've been toying with are rsyncing a dump of the db, or
> replication.
>
> Any ideas?

Give Slony (http://www.slony.info/) a try - the initial replication of the
entire DB takes a while, thereafter it only replicates changes (as they
happen).

We've been using it successfully (it has it's occasional problems like all
things) for over a year now replicating across a cluster (DB is also about
100GB+).

Regards
Henry