Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pk0WK-0003Os-HE for pgsql-admin@arkaria.postgresql.org; Wed, 05 Apr 2023 10:37:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pk0WJ-0003xr-4M for pgsql-admin@arkaria.postgresql.org; Wed, 05 Apr 2023 10:37:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pk0WI-0003xh-Pb for pgsql-admin@lists.postgresql.org; Wed, 05 Apr 2023 10:37:38 +0000 Received: from mail.ibu.de ([136.243.18.157] helo=ibu.de) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pk0WB-0002vt-RT for pgsql-admin@lists.postgresql.org; Wed, 05 Apr 2023 10:37:37 +0000 Received: from mail.ibu.de (localhost [127.0.0.1]) by ibu.de (8.16.1/8.16.1) with ESMTPS id 335AbOrH058048 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 5 Apr 2023 12:37:25 +0200 (CEST) (envelope-from np@ibu.de) Received: (from np@localhost) by mail.ibu.de (8.16.1/8.16.1/Submit) id 335AbO3u058045; Wed, 5 Apr 2023 12:37:24 +0200 (CEST) (envelope-from np@ibu.de) X-Authentication-Warning: mail.your-server.de: np set sender to np@ibu.de using -f Date: Wed, 5 Apr 2023 12:37:24 +0200 From: Norbert Poellmann To: "Capobianco, Tony" Cc: "pgsql-admin@lists.postgresql.org" Subject: Re: Barman and Hot Standby Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: "From: np@ibu.de" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Apr 04, 2023 at 10:24:20PM +0000, Capobianco, Tony wrote: Hi, in my understanding of your question streaming replication https://www.postgresql.org/docs/15/high-availability.html with Hot Standby: https://www.postgresql.org/docs/15/hot-standby.html is the way to go. Replication is a quite different task than to archive WAL files, what you have accomplished already with archive_command cheers Norbert Poellmann -- Norbert Poellmann EDV-Beratung email : np@ibu.de Severinstrasse 5 telefon: 089 38469995 81541 Muenchen, Germany telefon: 0179 2133436 > I have barman successfully running and performing scheduled backups. > > psql -d db -p 1234 -c "show archive_command" > archive_command > -------------------------------------------------------- > barman-wal-archive 10.11.12.13 cluster_name %p > > > psql -d db -p 1234 -c "show wal_level" > > wal_level > > ----------- > > replica > > > How can I add hot standby functionality to my environment if the archive_command is already defined with barman-wal-archive? > > Thanks. > Tony