El 04/07/16 a las 01:06, Adrian Klaver escribió:
> On 07/03/2016 06:21 PM, Patrick B wrote:
>>
>>
>> Not sure that would have mattered for the reasons below.
>>
>> You might want to take a look at the below:
>>
>> https://www.postgresql.org/docs/9.5/static/wal.html
>>
>> In particul
On 07/03/2016 06:21 PM, Patrick B wrote:
Not sure that would have mattered for the reasons below.
You might want to take a look at the below:
https://www.postgresql.org/docs/9.5/static/wal.html
In particular:
https://www.postgresql.org/docs/9.5/static/wal-intro.html
*slave_new:* server that needs a new copy of the DB
*slave01:* streaming replication slave
*My steps are:*
*1.* ssh slave_new
*2.* Stop postgres
*3.* rm -rf /var/lib/pgsql/9.2/data/*
*4.* ssh postgres@slave01 'pg_basebackup --pgdata=- --format=tar
--label=slave_new --progress --host=localhost --p
pg_basebackup --pgdata=- --format=tar --label=bkp_server --progress
--host=localhost --port=5432 --username=replicator --xlog-method=stream
Is that right? Once is finished, just need to restart postgres and set the
recovery.conf.restored.command?
Cheers
>
>
>>
> Not sure that would have mattered for the reasons below.
>
> You might want to take a look at the below:
>
> https://www.postgresql.org/docs/9.5/static/wal.html
>
> In particular:
>
> https://www.postgresql.org/docs/9.5/static/wal-intro.html
>
> Short version WAL files are essential to res
On 07/03/2016 05:36 PM, Patrick B wrote:
I don't have it now!
But I didn't know that postgres would need that file! If I knew it, I'd
have checked just after pg_basebackup started
Not sure that would have mattered for the reasons below.
You might want to take a look at the below:
https:/
I don't have it now!
But I didn't know that postgres would need that file! If I knew it, I'd
have checked just after pg_basebackup started
On 07/03/2016 05:23 PM, Patrick B wrote:
Yes, I read that!
However, I store the wal_files manually into three different servers.
I've double checked the files! I got over 500GB of wal_files when the
pg_basebackup finished, and still, wasn't enough.
Yes, but did you have the 16MB that are 0
Yes, I read that!
However, I store the wal_files manually into three different servers. I've
double checked the files! I got over 500GB of wal_files when the
pg_basebackup finished, and still, wasn't enough.
I'll re-do the steps but now using the STREAM option.
On 07/03/2016 03:17 PM, Patrick B wrote:
One more question:
Could I use pg_basebackup (or another tool like RSYNC) and re-sync the
data folder only with the missing data? for example... incremental? So I
wouldn't need to copy 2TB again?
That assumes the needed WAL files are still on the origin
On 07/03/2016 02:48 PM, Patrick B wrote:
Hi guys,
I'm currently using PostgreSQL 9.2.
One of my backup servers went down, and I had to re-sync the all the DB.
I used pg_basebackup and, of course, at the same time wal_archive.
Steps:
1 - Confirm the wal_files are being copied into the new serv
One more question:
Could I use pg_basebackup (or another tool like RSYNC) and re-sync the data
folder only with the missing data? for example... incremental? So I
wouldn't need to copy 2TB again?
Hi guys,
I'm currently using PostgreSQL 9.2.
One of my backup servers went down, and I had to re-sync the all the DB.
I used pg_basebackup and, of course, at the same time wal_archive.
Steps:
1 - Confirm the wal_files are being copied into the new server.
2 - Delete /var/lib/pgsql/9.2/data/*
3
13 matches
Mail list logo
