From: | Scott Mead <scottm(at)openscg(dot)com> |
---|---|
To: | Selva manickaraja <mavles78(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Timeline Issue |
Date: | 2011-02-17 01:36:57 |
Message-ID: | AANLkTimVJDSr0+tn265xz_d=RPUTua-s1MWdfLev_0ay@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Feb 16, 2011 at 8:29 PM, Selva manickaraja <mavles78(at)gmail(dot)com>wrote:
> Dear All,
>
> We have a primary running continous archiving to a secondary. We managed to
> test fail-over to the secondary by stopping the database in the primary.
> Then some transactions were tested in the secondary. It was acting well as a
> primary to accept both read and write.
>
> Now we want to revert this acting primary back to secondary and bring up
> the actual primary. We know that the secondary had gone out of synch in
> ahead of primary. So we do a PITR in this secondary before the time when the
> initial primary was brought down. Now the primary is up and the secondary is
> brought up as hot-standby. The secondary complaints that it cannot recover
> because its Timeline 2 does not match with the Timeline 1 of the primary.
>
Once you open the standby for use, it cannot be put back into standby mode.
You will need to rebuild the standby server from the primary.
--Scott
>
> How can this be resolved?
>
> Thank you.
>
> Regards,
>
> Selvam
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Mead | 2011-02-17 01:43:09 | Re: Timeline Issue |
Previous Message | Selva manickaraja | 2011-02-17 01:29:44 | Timeline Issue |