From: | Martin Marques <martin(dot)marques(at)2ndquadrant(dot)com> |
---|---|
To: | Edson Carlos Ericksson Richter <richter(at)simkorp(dot)com(dot)br>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Stand by server (9.6.6) with corrupt file |
Date: | 2017-12-23 11:58:42 |
Message-ID: | b808b563-277e-c4d1-74f4-29399ba8c822@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
El 22/12/17 a las 10:29, Edson Carlos Ericksson Richter escribió:
> Environment: PostgreSQL 9.6.6 installed from yum repository. Oracle
> Linux 7 EL x64. Dell servers with Raid 5 (hw).
>
>
> I was testing our database backup system (based on pgBarman), and
> discovered that one base file is corrupt in our standby database server.
> The file is OK in master server, but has 0 bytes in size in standby server.
How was the standby built? Did you use a recovered backup from barman or
did you clone from the master with some tool. An if it's the former,
which exact process did you use? (Using pg_basebackup would be the
safest way of cloning)
Regards,
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2017-12-23 16:59:38 | Re: Deadlock between concurrent index builds on different tables |
Previous Message | Martin Marques | 2017-12-23 11:40:18 | Re: Deadlock between concurrent index builds on different tables |