Hi,
I had the opportunity to work with barman. In my opinion, to configure
barman, you should have a separate dedicated system. Configure WAL
archiving properly to ensure that all transaction logs are streamed to
Barman like the following
archive_command = 'rsync %p barman@backup_server:/pa
Does anyone know a best practice when it comes to installing barman?
Would barman be on its own system or does it make sense to have it running
on a cascaded postgres server?
I'm just getting started with it so I'd like to see how others have
implemented its use in a variety of
Hi,
It's a typical error for brand new setup. After new backup setup do
$ barman switch-xlog --force --archive testdb
br
Kaido
On Wed, 10 Jan 2024 at 15:58, duc hiep ha wrote:
> Dear All,
>
> I am trying to use Barman to back up PostgreSQL, which is running in a
> Podman c
Dear All,
I am trying to use Barman to back up PostgreSQL, which is running in a
Podman container. However, I encounter the error "WAL archive: FAILED," as
shown below:
#barman check testdb
Server testdb:
WAL archive: FAILED (please make sure WAL shipping is set up)
PostgreSQL: OK
sup
b-include> for
additional information and caveats.
Are there any plans to add support for this to Barman?
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andr...@visena.com <mailto:andr...@visena.com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
forma...@lists.postgresql.org
Subject: Re: Barman
On Thu, Oct 31, 2019 at 05:29:34PM +, Daulat Ram wrote:
>Hi All,
>
>We have configured postgres 11.2 in streaming replication (primary &
>Standby) on docker and I am looking to initiate the Postgres backup
>using barman.
On Thu, Oct 31, 2019 at 05:29:34PM +, Daulat Ram wrote:
Hi All,
We have configured postgres 11.2 in streaming replication (primary &
Standby) on docker and I am looking to initiate the Postgres backup
using barman. As I know there are few options for taking backup using
barman.
R
Hi All,
We have configured postgres 11.2 in streaming replication (primary & Standby)
on docker and I am looking to initiate the Postgres backup using barman. As I
know there are few options for taking backup using barman.
RSYNC backup
Incremental Backups
Streaming Backup with continuous
Achilleas,
On 2/27/19 11:39 AM, Achilleas Mantzios wrote:
On 21/2/19 9:28 π.μ., Achilleas Mantzios wrote:
On 21/2/19 9:17 π.μ., Julie Nishimura wrote:
Does anyone use this solution? any recommenations?
Thanks!
Barman will fit most requirements. PgBackRest excels when WAL traffic
goes on
Sent: Thursday, 28 February 2019 7:41 PM
To: Achilleas Mantzios ; Ahmed, Nawaz
; pgsql-general@lists.postgresql.org
Subject: Re: Barman disaster recovery solution
On 2/28/19 9:21 AM, Achilleas Mantzios wrote:
> On 28/2/19 1:08 π.μ., Ahmed, Nawaz wrote:
>>
>> Hi,
>>
>&g
On 2/28/19 9:21 AM, Achilleas Mantzios wrote:
On 28/2/19 1:08 π.μ., Ahmed, Nawaz wrote:
Hi,
I believe the "file copy" method (listed in the table) in pgbackrest
is based on pg_basebackup, so i think it should be "pg_basebackup over
ssh" as pgbackrest internally calls pg_basebackup. David Ste
*
14 Rodborough Road, Frenchs Forest NSW 2086, Australia
*T* +61 2 9452 9027
na...@fast.au.fujitsu.com <mailto:na...@fast.au.fujitsu.com>
fastware.com.au <http://fastware.com.au/>
*From:*Achilleas Mantzios
*Sent:* Wednesday, 27 February 2019 8:40 PM
*To:* pgsql-general@lists.postgresql.or
On 27/2/19 6:52 μ.μ., Mark Fletcher wrote:
On Wed, Feb 27, 2019 at 1:39 AM Achilleas Mantzios mailto:ach...@matrix.gatewaynet.com>> wrote:
Hello, as promised here is my blog :
https://severalnines.com/blog/current-state-open-source-backup-management-postgresql
Nice blog post. If you'
On 2/27/19 4:48 PM, Achilleas Mantzios wrote:
On 27/2/19 4:16 μ.μ., David Steele wrote:
On 2/27/19 2:31 PM, Achilleas Mantzios wrote:
On 27/2/19 1:58 μ.μ., rich...@simkorp.com.br wrote:
Just to notice, I d o use backup from standby and WAL archive from
standby. It is possible. But you have to
On Wed, Feb 27, 2019 at 1:39 AM Achilleas Mantzios <
ach...@matrix.gatewaynet.com> wrote:
>
> Hello, as promised here is my blog :
>
> https://severalnines.com/blog/current-state-open-source-backup-management-postgresql
>
>
Nice blog post. If you're aiming for a comprehensive run down of tools, I
t, we used backup from primary server.
Using which tool?
Barman.
We have about 50 databases, half terabyte in total, primary and
standby separated geographically.
We had to write special app to monitor if standby is behind primary
(it compares the transaction id between primary and stand
tgresql.org>;
*Cc:*
*As! sunto:*Re: Barman disaster recovery solution
On 21/2/19 9:28 π.μ., Achilleas Mantzios wrote:
On 21/2/19 9:17 π.μ., Julie Nishimura wrote:
Does anyone use this solution? any recommenations?
Thanks!
Barman will fit most requirements. PgBackRest excels when WAL traffic g
o do meu Telefone LG/
-- Mensagem original--
*De: *Achilleas Mantzios
*Data: *qua, 27 de fev de 2019 06:40
*Para: *pgsql-general@lists.postgresql.org
<mailto:pgsql-general@lists.postgresql.org>;
*Cc:*
*As! sunto:*Re: Barman disaster recovery solution
On 21/2/19 9:28 π.μ., Achilleas Mantzi
On 27/2/19 4:16 μ.μ., David Steele wrote:
On 2/27/19 2:31 PM, Achilleas Mantzios wrote:
On 27/2/19 1:58 μ.μ., rich...@simkorp.com.br wrote:
Just to notice, I d o use backup from standby and WAL archive from standby. It is
possible. But you have to configure standby with option of wal archive "
On 2/27/19 2:31 PM, Achilleas Mantzios wrote:
On 27/2/19 1:58 μ.μ., rich...@simkorp.com.br wrote:
Just to notice, I d o use backup from standby and WAL archive from
standby. It is possible. But you have to configure standby with option
of wal archive "always".
I guess there are issues with it
*Cc:*
*As! sunto:*Re: Barman disaster recovery solution
On 21/2/19 9:28 π.μ., Achilleas Mantzios wrote:
On 21/2/19 9:17 π.μ., Julie Nishimura wrote:
Does anyone use this solution? any recommenations?
Thanks!
Barman will fit most requirements. PgBackRest excels when WAL traffic goes on 10 f
On 21/2/19 9:28 π.μ., Achilleas Mantzios wrote:
On 21/2/19 9:17 π.μ., Julie Nishimura wrote:
Does anyone use this solution? any recommenations?
Thanks!
Barman will fit most requirements. PgBackRest excels when WAL traffic goes on 10 files/day or more. I have written an article, not yet
Greetings,
* Edson Carlos Ericksson Richter (rich...@simkorp.com.br) wrote:
> No backup solution (no matter which one you choose) is 100% guaranteed: your
> disks may fail, your network mail fail, your memory may fail, files get
> corrupted - so, setup a regular "restore" to separate "test backup
Em 21/02/2019 04:17, Julie Nishimura escreveu:
Does anyone use this solution? any recommenations?
Thanks!
We do use it.
IMHO, those are minimum recommendations:
1) start using it! It's easy and robust.
2) for minimal impact over production servers, setup replicated servers
and create y
Am 21.02.19 um 08:17 schrieb Julie Nishimura:
Does anyone use this solution? any recommenations?
Thanks!
sure, many of our customers. why not?
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
On 21/2/19 9:17 π.μ., Julie Nishimura wrote:
Does anyone use this solution? any recommenations?
Thanks!
Barman will fit most requirements. PgBackRest excels when WAL traffic goes on 10 files/day or more. I have written an article, not yet publised, on a comparison on the 3 most known
Does anyone use this solution? any recommenations?
Thanks!
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
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
Hi All,
Hi all, I need some help over barman..Recently, I refreshed one of non-prod
environments with production database and I ran into this problem or rather
unforeseen point that I cannot change the system catalogs ownership to the
respective non prod owner account. And I really don't
El 05/10/18 a las 06:50, Rijo Roy escribió:
> Hello Experts,
>
> I have a server rhel 6.9 installed with barman 2.3 which is configured
> to take backup from Postgresql 10 installed in a remote host and the
> same is working.
You should upgrade to 2.4, although I can't see
Hello Experts,
I have a server rhel 6.9 installed with barman 2.3 which is configured to take
backup from Postgresql 10 installed in a remote host and the same is working.
I am trying to do a poc on streaming backup and streaming wal method by making
use of the pg_receivewal. I have already
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 with
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
Post
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 limitation
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 wh
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
>>&g
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-in
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 th
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 indica
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.
hange 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 ou
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 "typi
> 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}
barma
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
Hi Thomas,
On 4/11/18 3:14 AM, Thomas Poty wrote:
Sorry for answering only now but I just saw you answer only now.
> To be clear, I'm the original author and primary maintainer of
pgBackRest.
I am very happy to see guys like you to take time to answer me. Thank you
You are welcome. Users
DBs of different location.
I am very impatient to see "replication slot" support and "remote restore"
feature added.
Thank you for your time,
Regards,
Thomas
2018-03-09 15:56 GMT+01:00 David Steele :
> Hi Thomas,
>
> On 3/6/18 2:53 PM, Thomas Poty wrote:
&g
Hi Thomas,
On 3/6/18 2:53 PM, Thomas Poty wrote:
> Hello Community,
>
> I hesitate to use barman or pgBackRest. I have found a lot of common
> points between them and a few differences:
To be clear, I'm the original author and primary maintainer of
pgBackRest. I'll let
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 pgBackRest
Hi,
Just to say that i cannot using replication streaming but ssh shipping wal
works …
I’m trying barman product like that.
Thanks
nico
De : GALLIANO Nicolas
Envoyé : mardi 13 février 2018 10:15
À : Ahmed, Nawaz ; pgsql-gene...@postgresql.org
Objet : RE: Barman 2.3 errors
Hi
1/ thanks for
Hi
1/ thanks for your answer
2/ it’ right … the barman support list is better … sorry
3/ i’ve verified the pg replication slot :
postgres@postgres# SELECT slot_name, active, restart_lsn FROM
pg_replication_slots WHERE slot_type = 'physical' AND slot_name = 'barman'
Hi Nicolas,
I would like to take stab at this one, as i had recently worked on a demo of
barman. But like Michael Paquier said, it is better to check the information i
provide and the situation you are facing with the maintainers of the project.
Here is what i found.
The first thing is to
On Mon, Feb 12, 2018 at 03:23:22PM +, GALLIANO Nicolas wrote:
> I'm trying to backup a remote DB (9.6.6) using barman 2.3 but backup
> failed start.
> In barman.log i've such errors :
It would be a better idea to contact directly the maintainers of the
project here:
http
Hi,
I'm trying to backup a remote DB (9.6.6) using barman 2.3 but backup failed
start.
In barman.log i've such errors :
2018-02-12 16:18:23,852 [57691] barman.server ERROR: Check 'replication slot'
failed for server 'tcgepg96ddm'
2018-02-12 16:18:23,857 [576
57 matches
Mail list logo
