Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sU6k8-000VYK-Uc for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 15:39:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sU6j8-002KcE-BX for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 15:37:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sU6j7-002Kc4-SQ for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 15:37:58 +0000 Received: from mail-vk1-xa30.google.com ([2607:f8b0:4864:20::a30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sU6j5-0002eB-9p for pgsql-general@postgresql.org; Wed, 17 Jul 2024 15:37:57 +0000 Received: by mail-vk1-xa30.google.com with SMTP id 71dfb90a1353d-4f30f3be999so514660e0c.3 for ; Wed, 17 Jul 2024 08:37:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721230674; x=1721835474; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wVDP4Cx9vXEqWu9ySOzsguFpyFOF2QGTZvbQZDTaqvc=; b=atv9onQgSWUY4oXcTjGb7ra68QhJRC9uyrlk0SOiimAA4eNl8BKnsENybJtHrk1Mkl Tgwf4SkYxyppmxPAXVzHiTLGLpG/0bJ6/Ul6hMhS9BBRa+n4tgM6yk6pN7549jnURUDb cyP1L1M96JigOFgiIiYzvZD44zYZCKGiM38Idi+A1NqiAMaZun+NsbYWLysatP5WR9I5 hOg63bf/hzBb6qZyHzvw53He5HJVg/wimQhSqoPcubPv8cj6ygoblERT/SG5GKjcJ7HA VYTinybt8OhV1C2nVWIAw4HY6c4Cl2jn+yqFyYasAtm7uIBjyibBITkAvbzlwvp4pXIl YvuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721230674; x=1721835474; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=wVDP4Cx9vXEqWu9ySOzsguFpyFOF2QGTZvbQZDTaqvc=; b=xSDHpEu5URdsaPaEtJyVImF5pG+W/MwLJJ3vLVHxMlwcXPM3Hbu+wWqTlSKqkNzREa clotckhSEDDv9dQyS4SDlwzlPbvGj+UZmAXN5CRlr/C320hXA6gYMq+I3igxkHIOp8vH 3mNRGQ02lWq6jmNXX2+F63dtcveQYqdkokYisaCrsgf3zVTxkfN/5wOUbIdM6jiIS9VJ jlgZjyVS+fz6PVTtQqjyn9MVsvzwf7wEGng4yaJP2CCU/pHmmT2LKoazkkFMkUsdlSSh gS320vmAGk7S3ql1KFW/4cfJVXKRfTGouFqWCw2YwWcc4s7LJW8Uo1CxnEXTYqcgbhzt UKMg== X-Gm-Message-State: AOJu0YwqaAwYee1GRUrQxcGUwjG2wUUBMCBvEPdtzRLPlvRWe0jwyEpE Kk4IdfF0EsKUbjNx26+vMxNDvCpI4BRl6YyPW2aWhdV6bM50Rvfzf9Ar42Xaw6mNYg5En7BU9HB ynOo5xDE+zm3d2Mi7Mk7kuXN9+7Y= X-Google-Smtp-Source: AGHT+IG7CkI5h+9+sg/aDINZAbQVW7KbaLnpUFi1T11qC+IwvOH5uazVJQPNTAKluBkQdnhKcu2U92QHMO1xcg2B80o= X-Received: by 2002:a05:6122:1808:b0:4f2:ffa9:78b8 with SMTP id 71dfb90a1353d-4f4df8c9f3bmr2914868e0c.13.1721230672888; Wed, 17 Jul 2024 08:37:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kashif Zeeshan Date: Wed, 17 Jul 2024 20:37:43 +0500 Message-ID: Subject: Re: PgbackRest and EDB Query To: KK CHN Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000d58c82061d733e8c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d58c82061d733e8c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi On Wed, Jul 17, 2024 at 5:21=E2=80=AFPM KK CHN wrote: > Hi , > > I am trying pgbackrest(2.52.1) with postgresql( version 16) on a lab > setup on RHEL-9. Both PostgreSQL server and a remote Repository host > configured with pgbackrest and everything working fine as specified in th= e > documentation. > > note: here I am running postgres server and pgbackrest everything as > postgres user and no issues in backup and recovery. > > > > Query > 1. Is it possible to use PgBackrest with EnterpriseDB(EDB -16) for the > backup and recovery process? Or pgback works only with the community > PostgreSQL database ? > It support both community PG and EDB PG. > > > [ when I ran initdb script of EDB while installing EDB it creates the > enterpisedb as user and edb as initial database by the script. ] > Enterprisedb is the default user created by EDB. > > > when I try to create the stanza on the EDB server it throws error (paste= d > at bottom ). > > > > NOTE: > I know that my EDB running on port 5444 instead of 5432 and the dbnam= e > =3D edb instead of postgres, and user as enterpisedb instead of postgres= how > to specify these changes in the stanza creation step if EDB Supports > pgbackrest tool ? > You can enter this connection information in the PbBackRest Conf file for the stanza you create for your EDB Instance. e.g [global]repo1-path=3D/var/lib/edb/as15/backups [demo]pg1-path=3D/var/lib/edb/as15/datapg1-user=3Denterprisedbpg1-port=3D54= 44pg-version-force=3D15 Refer to following edb documentation https://www.enterprisedb.com/docs/supported-open-source/pgbackrest/03-quick= _start/ > OR Am I doing a waste exercise [if pgbackrest won't go ahead with EDB = ] > ? > > > Any hints much appreciated. > > Thank you, > Krishane > > > ERROR: > root@uaterssdrservice01 ~]# sudo -u postgres pgbackrest --stanza=3DOD_DM2 > --log-level-console=3Dinfo stanza-create > 2024-07-17 17:42:13.935 P00 INFO: stanza-create command begin 2.52.1: > --exec-id=3D1301876-7e055256 --log-level-console=3Dinfo --log-level-file= =3Ddebug > --pg1-path=3D/var/lib/pgsql/16/data --repo1-host=3D10.x.y.7 > --repo1-host-user=3Dpostgres --stanza=3DOD_DM2 > WARN: unable to check pg1: [DbConnectError] unable to connect to > 'dbname=3D'postgres' port=3D5432': connection to server on socket > "/tmp/.s.PGSQL.5432" failed: No such file or directory > Is the server running locally and accepting connections on that > socket? > ERROR: [056]: unable to find primary cluster - cannot proceed > HINT: are all available clusters in recovery? > 2024-07-17 17:42:13.936 P00 INFO: stanza-create command end: aborted > with exception [056] > [root@uaterssdrservice01 ~]# > > > > > --000000000000d58c82061d733e8c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0

On Wed, Jul 17, 2024 at 5:21=E2= =80=AFPM KK CHN <kkchn.in@gmail.co= m> wrote:
Hi ,=C2=A0

I am trying pgbackrest(2.52= .1)=C2=A0 with postgresql( version 16)=C2=A0 on=C2=A0 a lab setup on=C2=A0R= HEL-9. Both=C2=A0 PostgreSQL server and a remote Repository host configured= with pgbackrest and everything=C2=A0working fine as specified in the docum= entation.=C2=A0=C2=A0

note:=C2=A0 here I am runnin= g postgres server and pgbackrest everything as postgres user and no issues = in=C2=A0 backup and recovery.=C2=A0



Query
1. Is it possible to use=C2=A0 PgBackrest w= ith=C2=A0 EnterpriseDB(EDB -16) for the backup and recovery process?=C2=A0O= r pgback works only with the community=C2=A0 PostgreSQL database ?
It support both community PG and EDB PG.=C2=A0

<= /div>

[ when I ran=C2=A0 initdb script of EDB while inst= alling EDB it creates the enterpisedb=C2=A0 as user and edb as initial=C2= =A0 database by the script. ]
Enterprisedb= =C2=A0is the default user created by EDB.=C2=A0


when I try to create the stanza on the EDB server it throws= error=C2=A0 (pasted at bottom ).


<= br>
NOTE:=C2=A0
I know that=C2=A0 my EDB=C2=A0 running = on=C2=A0 port 5444 instead of=C2=A0 5432 and the dbname =3D edb instead of = postgres, and user as=C2=A0 enterpisedb instead of postgres how to specify = these changes in the stanza creation step if=C2=A0 EDB Supports pgbackrest = tool ?=C2=A0 =C2=A0
You can enter this connect= ion information in the PbBackRest Conf file for the stanza you create for y= our EDB Instance.
=C2=A0
e.g
[global]
repo1-path=3D/var/lib/edb/as15/backups

<=
span class=3D"gmail-token gmail-punctuation" style=3D"box-sizing:border-box=
">[demo]=

pg1-path=3D/var/lib/edb/as15/data
pg1-user=3Denterprisedb
pg1-port=3D5444
pg-version-force=3D15
Refer to following= edb documentation

=C2=A0
OR=C2=A0 =C2=A0Am I doing a waste exerci= se=C2=A0 [if pgbackrest won't go ahead with EDB ] ?


Any hints much appreciated.=C2=A0

=
Thank you,
Krishane


= ERROR:
root@uaterssdrservice01 ~]# sudo -u postgres pgbackrest --= stanza=3DOD_DM2 --log-level-console=3Dinfo =C2=A0stanza-create
2024-07-1= 7 17:42:13.935 P00 =C2=A0 INFO: stanza-create command begin 2.52.1: --exec-= id=3D1301876-7e055256 --log-level-console=3Dinfo --log-level-file=3Ddebug -= -pg1-path=3D/var/lib/pgsql/16/data --repo1-host=3D10.x.y.7 --repo1-host-use= r=3Dpostgres --stanza=3DOD_DM2
WARN: unable to check pg1: [DbConnectErro= r] unable to connect to 'dbname=3D'postgres' port=3D5432': = connection to server on socket "/tmp/.s.PGSQL.5432" failed: No su= ch file or directory
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Is the server running l= ocally and accepting connections on that socket?
ERROR: [056]: unable to= find primary cluster - cannot proceed
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: = are all available clusters in recovery?
2024-07-17 17:42:13.936 P00 =C2= =A0 INFO: stanza-create command end: aborted with exception [056]
[root@= uaterssdrservice01 ~]#




--000000000000d58c82061d733e8c--