From: | basti <mailinglist(at)unix-solution(dot)de> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg data backup from vps |
Date: | 2017-12-01 20:44:11 |
Message-ID: | a20ae6e3-3b19-3f4c-2543-6795dc43d604@unix-solution.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Replication is no backup.
Its more like a RAID.
That mean tubles that are delete on master by a mistake there are also
delete on slave.
correct me if i'am wrong.
Best regards,
basti
On 01.12.2017 21:10, Melvin Davidson wrote:
>
>
> On Fri, Dec 1, 2017 at 3:07 PM, Rob Sargent <robjsargent(at)gmail(dot)com
> <mailto:robjsargent(at)gmail(dot)com>> wrote:
>
>
>
> On 12/01/2017 12:56 PM, support-tiger wrote:
>
> To diversify risk, we would like to have a daily or weekly data
> backup stored in another location besides the VPS service we are
> using - pg_dump is great for the backup but transferring a
> growing db across the internet to a local machine disk seems
> slow - how are others handling this with postgresql ? Thks.
>
> So long as you're looking for more kinds of risk, why not stream the
> WAL files to another instance?
>
>
>
>>how are others handling this with postgresql ?
>
> One technique is to replicate to a slave on another server and do the
> pg_dump on the slave.
>
> --
> *Melvin Davidson*
> I reserve the right to fantasize. Whether or not you
> wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Rory Campbell-Lange | 2017-12-01 20:46:50 | Re: pg data backup from vps |
Previous Message | legrand legrand | 2017-12-01 20:38:59 | Re: PostgreSQL and Data Warehouse optimizations |