On 17/1/19 4:12 μ.μ., Jehan-Guillaume (ioguix) de Rorthais wrote:
On Thu, 17 Jan 2019 13:09:18 +0200
Achilleas Mantzios wrote:
Hello,
One strong point of barman IMHO is transparently converting an incremental
backup to a full backup for retention purposes, so retention specification is
far
On Thu, 17 Jan 2019 13:09:18 +0200
Achilleas Mantzios wrote:
> Hello,
>
> One strong point of barman IMHO is transparently converting an incremental
> backup to a full backup for retention purposes, so retention specification is
> far more liberal than with pgbackrest, and configuring for
Hello,
One strong point of barman IMHO is transparently converting an incremental backup to a full backup for retention purposes, so retention specification is far more liberal than with pgbackrest, and
configuring for incremental backup does not pose any limitations to the schedule of backups.
On 9/4/18 7:41 AM, Ron wrote:
> On 03/09/2018 08:56 AM, David Steele wrote:
>
>>> - 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
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
On 09/04/2018 08:55 AM, Ron wrote:
On 09/04/2018 10:51 AM, David Steele wrote:
[snip]
This will work, but I don't think it's what Ron is getting at.
To be clear, it is not possible to restore a database into an *existing*
cluster using pgBackRest selective restore. This is a limitation of
On 9/4/18 11:55 AM, Ron wrote:
> On 09/04/2018 10:51 AM, David Steele wrote:
> [snip]
>> This will work, but I don't think it's what Ron is getting at.
>>
>> To be clear, it is not possible to restore a database into an *existing*
>> cluster using pgBackRest selective restore. This is a
On 09/04/2018 10:51 AM, David Steele wrote:
[snip]
This will work, but I don't think it's what Ron is getting at.
To be clear, it is not possible to restore a database into an *existing*
cluster using pgBackRest selective restore. This is a limitation of
PostgreSQL file-level backups.
To do
On 9/4/18 11:24 AM, Joshua D. Drake wrote:
> On 09/04/2018 07:52 AM, Ron wrote:
>> On 09/04/2018 09:24 AM, Joshua D. Drake wrote:
>>> On 09/04/2018 07:14 AM, Ron wrote:
That was about barman, in the barman group. This is asking about
pgbackrest... :)
So: does pgbackrest
On 09/04/2018 10:24 AM, Joshua D. Drake wrote:
On 09/04/2018 07:52 AM, Ron wrote:
On 09/04/2018 09:24 AM, Joshua D. Drake wrote:
On 09/04/2018 07:14 AM, Ron wrote:
That was about barman, in the barman group. This is asking about
pgbackrest... :)
So: does pgbackrest have this ability
On 09/04/2018 07:52 AM, Ron wrote:
On 09/04/2018 09:24 AM, Joshua D. Drake wrote:
On 09/04/2018 07:14 AM, Ron wrote:
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"
On 09/04/2018 09:24 AM, Joshua D. Drake wrote:
On 09/04/2018 07:14 AM, Ron wrote:
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
On 09/04/2018 07:14 AM, Ron wrote:
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
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
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 a écrit :
> On 09/04/2018 07:14 AM, Thomas Poty wrote:
>
> > Do you just change the IP
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
> Do you just change the IP address of the "restore target"?
Do you expect a typical restore command? If yes, here is a small bash
script I use for check restore ...
barmanBackupID=""
barmanBackupServer=$1
if [ 1 -eq $# ]; then
echo ${barmanBackupServer}
barmanBackupID=$(barman
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
Hello Community,
I hesitate to use barman or pgBackRest. I have found a lot of common
points between them and a few differences:
About pgBarman, I like :
- be able restore on a remote server from the backup server
- use replication slots for backingup wal on the backup server.
About
19 matches
Mail list logo
