From: | Thomas Poty <thomas(dot)poty(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Barman versus pgBackRest |
Date: | 2018-09-04 13:44:31 |
Message-ID: | CAN_ctngN1CmNzW0nC+me-z_srgMhfVr4S0Q7+3Y2dSzQf7ZH=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Your problem looks like this one ;-)
https://groups.google.com/forum/#!topic/pgbarman/kXcEpSLhw8w
answer may help
Physical backup/restore operates on a whole cluster...
Le mar. 4 sept. 2018 à 14:47, Ron <ronljohnsonjr(at)gmail(dot)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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2018-09-04 13:46:42 | Re: psqlODBC |
Previous Message | Kumar, Virendra | 2018-09-04 13:38:43 | psqlODBC |