NEED REPLICATION SOLUTION -POSTGRES 9.1

[suhas.basavaraj12]

Hi,

We are planning to migrate our production databases to different
servers.We have around 8 servers with 8 different clusters.We are planning
t shuffle databases and make them as 7 cluster and migrate to new remote
servers .
We cannot use streaming replication as we are migrating different databases
from different clusters to one single cluster . This will be resulting in
huge downtime as data is huge .
Need expert advice on this scenario.Can we reduce downtime in any way ..??

Rgrds
Suhas



--
View this message in context: http://postgresql.1045698.n5.nabble.com/NEED-REPLICATION-SOLUTION-POSTGRES-9-1-tp5733939.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.

[Claudio Freire]

Post by suhas.basavaraj12
We are planning to migrate our production databases to different
servers.We have around 8 servers with 8 different clusters.We are planning
t shuffle databases and make them as 7 cluster and migrate to new remote
servers .
We cannot use streaming replication as we are migrating different databases
from different clusters to one single cluster . This will be resulting in
huge downtime as data is huge .
Need expert advice on this scenario.Can we reduce downtime in any way ..??

One time we had to do something like this (on a smaller scale), we used slony.

[Rick Otten]

I recommend SymmetricDS - http://www.symmetricds.org


-----Original Message-----
From: pgsql-performance-***@postgresql.org [mailto:pgsql-performance-***@postgresql.org] On Behalf Of suhas.basavaraj12
Sent: Wednesday, November 28, 2012 1:12 PM
To: pgsql-***@postgresql.org
Subject: [PERFORM] NEED REPLICATION SOLUTION -POSTGRES 9.1

Hi,

We are planning to migrate our production databases to different servers.We have around 8 servers with 8 different clusters.We are planning t shuffle databases and make them as 7 cluster and migrate to new remote servers .
We cannot use streaming replication as we are migrating different databases from different clusters to one single cluster . This will be resulting in huge downtime as data is huge .
Need expert advice on this scenario.Can we reduce downtime in any way ..??

Rgrds
Suhas



--
View this message in context: http://postgresql.1045698.n5.nabble.com/NEED-REPLICATION-SOLUTION-POSTGRES-9-1-tp5733939.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent via pgsql-performance mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance