Thanks for all your response.
I also thought abt having 2 setups for backup and replication so that even when slony fails I will always have the standby server (WAL shipping) to help me out.
I have another question regarding this. I also want to write these to the tape. Right now we have a cron job doing level 0,1,2,... backups of the other servers to the tape regularly. What is the good way to include postgres server backup to tape?
Thanks
josh
On Dec 28, 2007 9:29 AM, Glyn Astill <glynastill@xxxxxxxxxxx> wrote:
Hi Josh,
This is exactly the same setup I'm currently testing. For those
asking why use both WAL shipping and slony, it's simple; this means
we have no single point of failure. If slony stops replicating
because we mess up a replication set or our shipping method (NFS)
falls on its ass, at least we still have some replication going.
We have to use slony, like you we need a replica to take the load off
of our main system, this is mainly for our reporting processes.
Glyn
--- Josh Harrison <joshques@xxxxxxxxx> wrote:
> Hi,
> We are trying to use slony and WAL shipping for warm standby for
> replication
> with postgresql. Currently our systems are in oracle and we r
> checking the
> feasibility to migrate to postgres. Replication is one major issue
> here.
> Though everything seems to be working fine in our test environment,
> we just
> want the assurance that Slony and WAL shipping is used by other
> large
> production systems and running successfully.
> What are the other large 24x7 productions systems that use slony
> and the
> other WAL archiving of postgresql successfully?
>
> Thanks
> josh
>___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
