| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | chinnaobi <chinnaobi(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How to avoid base backup in automated failover |
| Date: | 2012-06-26 15:30:43 |
| Message-ID: | CA+TgmoZmsr_14PzjG-2aHL1h=00tZ5sB4xFW6jvRnFyjZ0W04Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, Jun 4, 2012 at 9:14 AM, chinnaobi <chinnaobi(at)gmail(dot)com> wrote:
> Recently I was writing an application to implement automated failover with
> env: Two 2008 R2 servers, Network area storage, asynchronous replication,
> WAL archive on primary enabled.
>
> Is there any way to avoid starting standby server always from base backup in
> automated failover. I see the database is growing huge. I can't keep doing
> base backup every day.
>
> Please suggest solution
The usual solution is to configure the standby as a warm or hot
standby, so that logs are continuously replayed there. Then if the
master dies, you only have to wait for replication to catch up before
promoting.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2012-06-26 16:13:44 | Re: Calculating Replication Lag - units |
| Previous Message | David Kerr | 2012-06-26 15:25:32 | Re: Calculating Replication Lag - units |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2012-06-26 15:33:42 | Re: empty backup_label |
| Previous Message | Euler Taveira | 2012-06-26 15:29:33 | Re: libpq compression |