| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
| Cc: | Benjamin Arai <barai(at)cs(dot)ucr(dot)edu>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Syncing Databases Weekly |
| Date: | 2006-02-07 19:09:44 |
| Message-ID: | 43E8F078.8090402@commandprompt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Brad Nicholson wrote:
> Joshua D. Drake wrote:
>
>> 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.
>>
> Slony's log shipping is another option.
Oh cool... I didn't know Slony could do that. Glad to hear it.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jao | 2006-02-07 19:37:21 | B-tree performance improvements in 8.x |
| Previous Message | Brad Nicholson | 2006-02-07 18:34:06 | Re: Syncing Databases Weekly |