Strategy for moving a large DB to another machine with least possible down-time

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Strategy for moving a large DB to another machine with least possible down-time
Date: 2014-09-21 11:36:18
Message-ID: VisenaEmail.57.45219778166c5146.14897f82eab@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all.   PG-version: 9.3.5   I have a DB large enough for it to be impractical
to pg_dump/restore it (would require too much down-time for customer). Note
that I'm noe able to move the whole cluster, only *one* DB in that cluster.  
What is the best way to perform such a move, can i use PITR, rsync +
webl-replay magic, what else? Can Barman help with this, maybe?   Thanks.   --
Andreas Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com> www.visena.com
<https://www.visena.com> <https://www.visena.com>

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2014-09-21 11:51:00 Re: Strategy for moving a large DB to another machine with least possible down-time
Previous Message David G Johnston 2014-09-20 18:46:53 Re: cloning database