Re: Barman versus pgBackRest - Mailing list pgsql-general

From Ron
Subject Re: Barman versus pgBackRest
Date
Msg-id 5d1e08a4-e7c9-0d32-7d01-5b1c76cc67ef@gmail.com
Whole thread Raw
In response to Re: Barman versus pgBackRest  (Thomas Poty <thomas.poty@gmail.com>)
Responses Re: Barman versus pgBackRest
List pgsql-general

That was about barman, in the barman group.  This is asking about pgbackrest...  :)

So: does pgbackrest have this ability which barman does not have?  The "--db-include" option seems to indicate that you can restore a single db, but does indicate whether or not you can rename it.


On 09/04/2018 08:44 AM, Thomas Poty wrote:
Your problem looks like this one ;-)
answer may help

Physical backup/restore operates on a whole cluster...

Le mar. 4 sept. 2018 à 14:47, Ron <ronljohnsonjr@gmail.com> a écrit :
On 09/04/2018 07:14 AM, Thomas Poty wrote:
> Do you just change the IP address of the "restore target"?
Do you expect a typical restore command?

I'm investigating barman and pgBackRest to replace our exitsing NetBackup system, so don't know what you mean by "typical restore command".

Here are our typical use cases:

1. If my barman backup server has full backups, diffs and WALs for database server MAIN_PG_SERVER, which hosts databases D1, D2 and D3, how much work is it to do a PITR restore of D2 to a different Pg server?

2. Can I restore an older copy of database D2 to MAIN_PG_SERVER, giving it a new name (so that now there would be databases D1, D2, D3 and D2_OLD)?  That's pretty trivial on SQL Server, and something I've had to do before so the operations staff can research a problem.)

Thanks

--
Angular momentum makes the world go 'round.

--
Angular momentum makes the world go 'round.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: psqlODBC
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Barman versus pgBackRest