Re: Barman disaster recovery solution
От | Edson Carlos Ericksson Richter |
---|---|
Тема | Re: Barman disaster recovery solution |
Дата | |
Msg-id | cb99f1bb-27ad-3293-8f0a-1dbad5df0c06@simkorp.com.br обсуждение исходный текст |
Ответ на | Re: Barman disaster recovery solution (Achilleas Mantzios <achill@matrix.gatewaynet.com>) |
Список | pgsql-general |
Em 27/02/2019 12:12, Achilleas Mantzios escreveu: > On 27/2/19 5:04 μ.μ., Edson Carlos Ericksson Richter wrote: >> >> Em 27/02/2019 09:31, Achilleas Mantzios escreveu: >>> On 27/2/19 1:58 μ.μ., richter@simkorp.com.br wrote: >>>> Just to notice, I d o use backup from standby and WAL archive from >>>> standby. It is possible. But you have to configure standby with >>>> option of wal archive "always". >>> >>> I guess there are issues with it. If this was so easy then pgbarman >>> and pgbackrest would support it out of the box. >> >> >> >> Well, >> >> >> This setup it is working really well for past two years; prior to >> that, we used backup from primary server. > Using which tool? Barman. >> >> We have about 50 databases, half terabyte in total, primary and >> standby separated geographically. >> >> We had to write special app to monitor if standby is behind primary >> (it compares the transaction id between primary and standby). >> >> For eight years, we had no single failure from PgSQL databases (using >> since 9.0 and today on 9.6), replication is for "just in case" data >> center unavailability, and backup is for disaster recovery (in case >> two data centers in different states from different vendors get out >> of work at same time). >> >> >> But we give no chance to bad luck: we monitor replication status >> every 2 minutes, we make full backup every 2 days with incremental >> backup in between, and test all backups on a recover server every >> day. As pointed, we have no single database failure that required to >> use the replication server or the backup server, but we will not >> lower the attention. > Which means you tested your backups? Recover and run our main app on it. Regards, Edson >> >> >> Regards, >> >> >> Edson >> >> >>> >>>> >>>> Just my 2c, >>>> >>>> Edson Richter >>>> >>>> /Enviado do meu Telefone LG/ >>>> >>>> ------ Mensagem original------ >>>> *De: *Achilleas Mantzios >>>> *Data: *qua, 27 de fev de 2019 06:40 >>>> *Para: *pgsql-general@lists.postgresql.org >>>> <mailto:pgsql-general@lists.postgresql.org>; >>>> *Cc:* >>>> *As! sunto:*Re: Barman disaster recovery solution >>>> >>>> On 21/2/19 9:28 π.μ., Achilleas Mantzios wrote: >>>>> On 21/2/19 9:17 π.μ., Julie Nishimura wrote: >>>>>> Does anyone use this solution? any recommenations? >>>>>> >>>>>> Thanks! >>>>> >>>>> Barman will fit most requirements. PgBackRest excels when WAL >>>>> traffic goes on 100000 files/day or more. I have written an >>>>> article, not yet publised, on a comparison on the 3 most known >>>>> solutions. Will post a link as soon as it gets published. >>>> >>>> Hello, as promised here is my blog : >>>> https://severalnines.com/blog/current-state-open-source-backup-management-postgresql >>>> >>>> >>>>> >>>>> -- >>>>> Achilleas Mantzios >>>>> IT DEV Lead >>>>> IT DEPT >>>>> Dynacom Tankers Mgmt >>>> >>>> >>>> -- >>>> Achilleas Mantzios >>>> IT DEV Lead >>>> IT DEPT >>>> Dynacom Tankers Mgmt >>> >>> >>> -- >>> Achilleas Mantzios >>> IT DEV Lead >>> IT DEPT >>> Dynacom Tankers Mgmt >> > >
В списке pgsql-general по дате отправления: