From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Joao Miguel Ferreira <joao(dot)mc(dot)ferreira(at)criticalsoftware(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: replicating to a stopped server |
Date: | 2007-10-12 19:09:15 |
Message-ID: | F74877E2-2B68-4F6A-8FEB-5F2B4F00D308@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Oct 12, 2007, at 1:59 PM, Richard Huxton wrote:
> Joao Miguel Ferreira wrote:
>> Hello,
>> I have a 'strange' situation:
>> I need to make a replica copy of my database to a
>> reduntant
>> spare
>> computer.
>> The reduntant computer is not running postgres,
>> but postgres is
>> installed. The redundant computer is running in a special
>> run-level (I'm
>> talking Linux here) in which Pg is _not_ running.
>> When the primary computer crashes the redundant
>> one will be
>> rebooted in
>> 'normal' mode and Postgres must be started with the databases
>> from the
>> replica.
>
> You could use WAL archiving, but you'll want a fairly regular full-
> backup of PG's files otherwise the recovery could take a long time.
> See Ch 23 of the manuals for details.
Are you restricted to keep that second server in that special run-
level? If not, I'd consider using pg_standby with WAL archiving to
keep your failover server at most a handful of minutes behind.
Erik Jones
Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Relyea, Mike | 2007-10-12 19:21:00 | Re: Out of memory with ODBC |
Previous Message | Richard Huxton | 2007-10-12 18:59:30 | Re: replicating to a stopped server |