Re: Barman versus pgBackRest - Mailing list pgsql-general

From David Steele
Subject Re: Barman versus pgBackRest
Date
Msg-id af69693f-91cf-21f3-e795-c5fdd7a3ff7f@pgmasters.net
Whole thread Raw
In response to Re: Barman versus pgBackRest  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general
Hi Ron,

On 9/4/18 7:41 AM, Ron wrote:
> On 03/09/2018 08:56 AM, David Steele wrote:
> [snip]
>>> About pgBarman, I like :
>>> - be able restore on a remote server from the backup server
>> This a good feature, and one that has been requested for pgBackRest. You
>> can do this fairly trivially with ssh, however, so it generally hasn't
>> been a big deal for people.  Is there a particular reason you need this
>> feature?
> 
> (Sorry to dredge up this old thread.)
> 
> Do you just change the IP address of the "restore target"?

[I'll assume you wanted to hear about pgBackRest here since we discussed
it down thread.]

Generally restores are done from the database server, but if you want to
run a restore from the backup server you can run it via ssh:

ssh user@pg-server pgbackrest [...]

> 
>>> - use replication slots for backingup wal on the backup server.
>> Another good feature.  We have not added it yet because pgBackRest was
>> originally written for very high-volume clusters (100K+ WAL per day) and
>> our parallel async feature answers that need much better.  We recommend
>> a replicated standby for more update-to-date data.
> 
> Every N minutes you copy the WAL files to the backup server?
> 
> 

-- 
-David
david@pgmasters.net


pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Barman versus pgBackRest
Next
From: David Steele
Date:
Subject: Re: Barman versus pgBackRest