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 1sU3fY-0006c1-Og for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 12:22:04 +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 1sU3eY-000J4W-3R for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 12:21:02 +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 1sU3eX-000J4N-Oc for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 12:21:02 +0000 Received: from mail-yw1-x112c.google.com ([2607:f8b0:4864:20::112c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sU3eV-00017E-HY for pgsql-general@postgresql.org; Wed, 17 Jul 2024 12:21:00 +0000 Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-65f880c56b1so42123667b3.3 for ; Wed, 17 Jul 2024 05:20:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721218859; x=1721823659; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=LSJqrKb8l59cTLbVeCKKbzRV4VtG70JDeE4y0RBEZcI=; b=ZwjdltAHvEoZpsawQSWzUm9P4fJoXDHCk/3ZBQXI1X7d8DDKxYxrZcR6U8NrOvv+vH h3HNQ2KMQxAmoAT6TbNnoibQAMkqCJ+ZWlnKa+VUNzHgM0OWsafJBTqom4CRXdY+vME6 fV8/AdmO3UNZTIJA4e3wDbeFl/Y8M6pD0M3seNBOcPPZg3xueHkVMRFlQfuPPQ9ZijfI RNDFWUOUDEAUXkejQYaB3OFdL3xxh8/fNeuvR3LtW0g+5zGxtLEU5oxcaDedyW0Rlpjf MndlZHp6Rg4eLG7hEBSvWG2gdORKavk66oINKRjqioMkphPYVHmEYmOa6TfwwjhEIvZ/ FJdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721218859; x=1721823659; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=LSJqrKb8l59cTLbVeCKKbzRV4VtG70JDeE4y0RBEZcI=; b=sz2dNxo5BzqiHkKyBxUR/OipdUssZx6iZ3SkY9sp5qN9OOicLk2fO2BvcNMC2hM3k/ /fdJuHSKeFnIr53+znVw7Gg2O+78IuCfKSrk4hMKmKI+rjHb/ZAcMRdeLoYGHfqZeHCs AzU4/TnKVy2kN9a4hW8KUBsOTYxZMPGOn8kp/6DdWzC4el6EYFQaAISxBEw+VtypddHN MKAqaqJEGvwVY4HEOyvzuDDbqBnErElx2WWD4V19wyape5sQKMAQv/d4ihSQAWP61AA7 +WrzKaFIR5NsOcLhlYljPRTUZ5fDbDhJ7hbQmJ3DNuew+O4nC/YZksVUd3To6/mwk5Hg 9ifQ== X-Gm-Message-State: AOJu0Yw//EITXIBMFpn6stPZcVaG6fwA6fNL64g+OggzJBEabwEspY9O IjHgvKACY5zZalyF369QQcK2Scsilip3B3b6+R3zrSpvRAMvlgz8Hz0YPvmmRdrdZBDoXiWus1V fZgsuCDZ1f/+bNMQxlOALr0iwCsodpK1p X-Google-Smtp-Source: AGHT+IEnKTBfF99PZ4u1spefFEt7L8xsAjl2LOJekTYE9+jT4YbFgLF4t//ujX2065F871+BTSQqfEjv4H1jXSeuxHo= X-Received: by 2002:a81:7c02:0:b0:61a:ccb0:7cdd with SMTP id 00721157ae682-66500573b1emr17483087b3.46.1721218858459; Wed, 17 Jul 2024 05:20:58 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Wed, 17 Jul 2024 18:00:01 +0530 Message-ID: Subject: PgbackRest and EDB Query To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000a3ad9c061d707e2c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a3ad9c061d707e2c Content-Type: text/plain; charset="UTF-8" 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 the 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 ? [ when I ran initdb script of EDB while installing EDB it creates the enterpisedb as user and edb as initial database by the script. ] when I try to create the stanza on the EDB server it throws error (pasted at bottom ). NOTE: I know that my EDB running on port 5444 instead of 5432 and the dbname = 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 ? 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=OD_DM2 --log-level-console=info stanza-create 2024-07-17 17:42:13.935 P00 INFO: stanza-create command begin 2.52.1: --exec-id=1301876-7e055256 --log-level-console=info --log-level-file=debug --pg1-path=/var/lib/pgsql/16/data --repo1-host=10.x.y.7 --repo1-host-user=postgres --stanza=OD_DM2 WARN: unable to check pg1: [DbConnectError] unable to connect to 'dbname='postgres' port=5432': 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 ~]# --000000000000a3ad9c061d707e2c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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=A0RH= EL-9. Both=C2=A0 PostgreSQL server and a remote Repository host configured = with pgbackrest and everything=C2=A0working fine as specified in the docume= ntation.=C2=A0=C2=A0

note:=C2=A0 here I am running= postgres server and pgbackrest everything as postgres user and no issues i= n=C2=A0 backup and recovery.=C2=A0


=
Query
1. Is it possible to use=C2=A0 PgBackrest wi= th=C2=A0 EnterpriseDB(EDB -16) for the backup and recovery process?=C2=A0Or= pgback works only with the community=C2=A0 PostgreSQL database ?


[ when I ran=C2=A0 initdb script of EDB whil= e installing EDB it creates the enterpisedb=C2=A0 as user and edb as initia= l=C2=A0 database by the script. ]


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



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

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

<= div>
Any hints much appreciated.=C2=A0

Thank you,
Krishane


ER= ROR:
root@uaterssdrservice01 ~]# sudo -u postgres pgbackrest --st= anza=3DOD_DM2 --log-level-console=3Dinfo =C2=A0stanza-create
2024-07-17 = 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 --p= g1-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': c= onnection to server on socket "/tmp/.s.PGSQL.5432" failed: No suc= h file or directory
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Is the server running lo= cally and accepting connections on that socket?
ERROR: [056]: unable to = find primary cluster - cannot proceed
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: a= re 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 ~]#




--000000000000a3ad9c061d707e2c--