From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Benjamin Arai <barai(at)cs(dot)ucr(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Syncing Databases Weekly |
Date: | 2006-02-07 17:45:31 |
Message-ID: | 43E8DCBB.1050308@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Benjamin Arai wrote:
> Hi,
>
> I am familiar with applications like slony for replications, I am
> looking for a technique for syncing a very large database every week
> for backup and redundancy purposes. More specifically, I do all my
> writes to a main server once a week, at the end of the updates I would
> like to automatically copy all of the data to a second server as a
> live backup in case the main system ever goes down.
You could use batch replication via Mammoth Replicator or PITR.
Joshua D. Drake
>
> My initial thought involved streaming a pg_dump from main server to
> the backup server every week and doing the pg_restore on the receiving
> side. I initially tried using slony but it just took too long for
> slony to catch up and there is no real need to do replication during
> the update. Does that seem like the best option?
>
> *Benjamin Arai*
> barai(at)cs(dot)ucr(dot)edu <mailto:barai(at)cs(dot)ucr(dot)edu>
> http://www.benjaminarai.com <http://www.benjaminarai.com/>
>
> **
From | Date | Subject | |
---|---|---|---|
Next Message | Jason C. Leach | 2006-02-07 17:54:20 | Why pg_hba not in table? |
Previous Message | Philippe Ferreira | 2006-02-07 17:43:43 | Re: SELECT with REAL... |