From: | Aldo Sarmiento <aldo(at)bigpurpledot(dot)com> |
---|---|
To: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Backups |
Date: | 2018-01-19 02:19:38 |
Message-ID: | CAHX=r6yPw-AirfnRCMG=NrTyRM0O9_HHiSCYS9r_ZU+XNaX=hQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I have had lots of success using streaming replication for potential
failover as well as read only hot stand by to assist with my master db.
Additionally we use pg backrest for PITR in the event that we need to roll
back for some unforeseen reason (hacking, corruption, etc).
*Aldo Sarmiento*
President & CTO
8687 Research Dr, Irvine, CA 92618
*O*: (949) 223-0900 - *F: *(949) 727-4265
aldo(at)bigpurpledot(dot)com | www.bigpurpledot.com
On Thu, Jan 18, 2018 at 6:16 PM, Azimuddin Mohammed <azimeiu(at)gmail(dot)com>
wrote:
> Hello admins,
> What is thr best backup strategy?
> I am planning to setup my pg cluster with streaming replication.
> My criteria
> 1. I should not be restarting my master server and slave.
> 2. Shiuld take a huge performace cpu or memory (Ram) consumption.
> 3. Compression is ok.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Der Fluch | 2018-01-19 03:54:19 | Can not execute DDL in SSIS. |
Previous Message | Azimuddin Mohammed | 2018-01-19 02:16:29 | Backups |