Re: New Slave - timeline ERROR

From: "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: New Slave - timeline ERROR
Date: 2016-01-09 21:54:56
Message-ID: CAE_gQfWbCqn+EvTh5hYqFk3+XVix6RDphS5gOnx+DeDp2vkGqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

If you are able to stop Postgres on the slave you are taking the base
> backup from, you could do this:

I'm not... the data base is 2 TB.
So, a RSYNC would take DAYS..... And I'm not able to stop the SLAVE for
that long time

Lucas

Lucas Possamai

kinghost.co.nz
<http://forum.kinghost.co.nz/memberlist.php?mode=viewprofile&u=2&sid=e999f8370385657a65d41d5ff60b0b38>

On 10 January 2016 at 10:53, bricklen <bricklen(at)gmail(dot)com> wrote:

> On Sat, Jan 9, 2016 at 1:49 PM, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)com
> > wrote:
>
>> Hi,
>>
>> If the master is successfully ships WALs to the slave you are setting up
>>> you do not need the "stream" option.
>>
>>
>> yes.. the master is successfully shipping the WALs....
>>
>> Is there anything else? Help, please hehehehe
>>
>
> If you are able to stop Postgres on the slave you are taking the base
> backup from, you could do this:
>
> 1). Stop postgres on slave1
> 2). Rsync slave1 to slave2 to copy only the deltas.
> 3). When you start up slave2 the WALs that the master has shipped to
> slave2 should apply and bring your system up to consistency.
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message bricklen 2016-01-09 21:59:41 Re: New Slave - timeline ERROR
Previous Message bricklen 2016-01-09 21:53:10 Re: New Slave - timeline ERROR