From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg data backup from vps |
Date: | 2017-12-01 20:10:09 |
Message-ID: | CANu8FizZp2qOjUv06E=+MFhg3wTr8XNaR6LH=CaR2dZzrX8jQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Dec 1, 2017 at 3:07 PM, Rob Sargent <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 | Joshua D. Drake | 2017-12-01 20:36:06 | Re: pg data backup from vps |
Previous Message | Rob Sargent | 2017-12-01 20:07:33 | Re: pg data backup from vps |