Re: Migrate postgres to newer hardware

From: Szymon Guz <mabewlun(at)gmail(dot)com>
To: Renato Oliveira <renato(dot)oliveira(at)grant(dot)co(dot)uk>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Migrate postgres to newer hardware
Date: 2010-03-30 11:28:31
Message-ID: e4edc9361003300428s690df286q7f817cb9d936043f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

2010/3/30 Renato Oliveira <renato(dot)oliveira(at)grant(dot)co(dot)uk>

> Dear All,
>
> What would be the easiest and fastest way to migrate Postgres 8.2.24 32 BIT
> to a new server 64 Bit.
>
> The existing server runs on 32 bit architecture and has a database as big
> as 160GB.
>
> We initially thought of using PITR, but as one of the PITR requirements is
> both machines need to be similar.
>
> This similarity needs to be even in architecture? I think I read something
> which says “Yes”.
>
> If we cannot use PITR what would be the best approach, we can’t have down
> time I am afraid.
>
> Any ideas or suggestions would be very welcome.
>
>
>
I'd use Slony as a replication tool so the data would be copied to the new
serwer while the old still works. After initial copy Slony will copy changes
made during making the copy. Later (when the replication lag is small) it
should be enough to stop application, reconfigure it for the new database,
get rid of replication so the new slave database will restore all triggers
and then start the application for using the new database.
Slony uses pure SQL for copying the data so there is no problem with the
differences in the hardware.

regards
Szymon Guz

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Renato Oliveira 2010-03-30 11:36:00 Re: Migrate postgres to newer hardware
Previous Message Renato Oliveira 2010-03-30 11:18:36 Migrate postgres to newer hardware