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 1sjX4A-001Yds-MU for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 04:47:26 +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 1sjX47-00EfKS-N2 for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 04:47:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjX47-00EfKK-BN for pgsql-general@lists.postgresql.org; Thu, 29 Aug 2024 04:47:23 +0000 Received: from mail-yw1-x1130.google.com ([2607:f8b0:4864:20::1130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjX44-0021ra-5Y for pgsql-general@postgresql.org; Thu, 29 Aug 2024 04:47:23 +0000 Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-6b6b9867faaso2475177b3.2 for ; Wed, 28 Aug 2024 21:47:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724906839; x=1725511639; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=V9hoerzgyJ4b3Qoy81B3B1521Pbf8S6WjB0eohviX6M=; b=bqLL3XhAXiHTwCV9U65uRR5KVHfUygUJ0f72F7o6s/OnkUbCQKOEbIdHJ3kXNmJn2F uQfwLy/EYFwzMXTxIEuZyaUZHM2FMFMT/zlG8MXrvR7RXrn48e5FtrYpoJFyfGRGvKli NjIbTR8Qx+Ky12MeS+LcHE47TZq/wRXtlCwyDghbaM0WDaqTAHYPNijLYHLQDASzpkBg NuyAXvtMnhk9iXcX7D6X+gV+tRuO9xF3eu48Dz7C3MVDO5ffyHI2Skv/VTRqX0xRnX0o u25BblI575qHWxFBT7djilrJMVCjdj6QBFzsw3TVeARfLIwo/Nu+LCTHC0G9YXXFh3aK SO2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724906839; x=1725511639; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=V9hoerzgyJ4b3Qoy81B3B1521Pbf8S6WjB0eohviX6M=; b=DSf4LUDZlWc7eVYvT4907d+o4LPu1QekeUaej77423mhMLEXki5TmiIzX1VHNE8nuW yw22K2V2rYmm9vbRizxvGn8a2UYFCCj9nNHGCZA/+P9ul0TZdsriuqIb1gNmqrqrhG+j yXZTNImj2A7bK9izZ6PtPsr8WrMCNm6Z7BTuSqLy110AySDfHuRApzWdMRAfN75WfqKd lx8yEHb8g6RpnJX/0P58sB9DLIGhoXk+VZTrKsSdY4XDsCnbUYihjjY8TCZPv8QtiQj/ iuXz9B4kBROFmIjkQrxYy1f+p+aXxvkUdspiMRxOBI7eDQL+i4OHBXKS0Nq3PN4TNw+k 2UyQ== X-Gm-Message-State: AOJu0Yzl+Z0pQBUVzjQogTVomEeJMniaxAEXkXedGI1gDgF4hsykwBFk zfTPAAYlgXQWbbMGRy0so9PqmNegIZirFaNpCHBBUBAED7izCRI1wliwvQVe8pIUiyGvUoUSCRB OHQdZzam+zYfob94UxgI5+J9obbzSlt4R X-Google-Smtp-Source: AGHT+IE1EWMaif+nQBRPeeYgl2yNrXhr6Qs3jaM+0etrO9dh1d4DJ8//9M6d/HNESFUqwdCVCvtEvGS2xCQGNj95o2w= X-Received: by 2002:a05:690c:6386:b0:6d1:2779:ba2e with SMTP id 00721157ae682-6d277a780a8mr19604327b3.28.1724906839027; Wed, 28 Aug 2024 21:47:19 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Thu, 29 Aug 2024 10:17:27 +0530 Message-ID: Subject: PgbackRest stanza creation : on DB server or both DB and Repo server ? To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000006938d10620cb2ba4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006938d10620cb2ba4 Content-Type: text/plain; charset="UTF-8" List, I am configuring the Pgbackrest ( RHEL9.4 , EPAS 16 , PgbackRest 2.52.1 ) on two servers.(Database cluster server and Repo Server). Query.1 Do I need to create stanza on both servers ( DB server EPAS16 User : enterprisedb, as well as on RepoServer user: postgres ) 1. only creating stanza either at DB Server but not on RepoServer is sufficient? OR I have to create the stanza on both servers as follows ? on DB server ( RHEL 9.4, EPAS 16 : DB user is : enterprisedb ) ]#sudo -u enterprisedb pgbackrest --stanza=Repo --log-level-console=info stanza-create Initially It complains about another pgbackrest running and aborted the stanza-creation second attempt : Without complaining about anything the stanza creaton successful :) I couldn't understand why it complained about another pgbackrest running in the first place ? ( before running stanza creation on DB server, I first tried the stanza creation on RepoServer as ]# sudo -u postgres pgbackrest --stanza=Repo --log-level-console=info stanza-create On Repo server : ( postgres user for Repo server, but no PG installed only user postgres is created for backup purpose) ]# #sudo -u postgres pgbackrest --stanza=Repo --log-level-console=info stanza-create But no success(on multiple stanza creation attempts) : It always aborted with a message another pgbackrest is running .. So Only stanza creation has to performed either on DB Server or RepoServe but not on both servers ? Kindly shed some light on this. Thank you, Krishane --0000000000006938d10620cb2ba4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
List,=C2=A0

=C2=A0I am configuring the= =C2=A0 =C2=A0Pgbackrest=C2=A0 ( RHEL9.4=C2=A0,=C2=A0 EPAS 16=C2=A0 , Pgback= Rest 2.52.1 )=C2=A0 on two servers.(Database cluster server and=C2=A0 =C2= =A0Repo Server).

Query.1=C2=A0 Do I need to create stanza on both=C2= =A0 =C2=A0servers=C2=A0 =C2=A0( DB server EPAS16 User : enterprisedb,=C2=A0= =C2=A0 as well as on=C2=A0 RepoServer=C2=A0 =C2=A0user: postgres=C2=A0 =C2= =A0)

1.=C2=A0 only creating stanza=C2=A0 either at= =C2=A0 DB Server=C2=A0 but not on=C2=A0 RepoServer is sufficient?=C2=A0 OR= =C2=A0 I have to create the=C2=A0 stanza on both servers as follows ?
=

on DB server=C2=A0 =C2=A0( RHEL 9.4, EPAS 16=C2=A0 : DB= user is : enterprisedb=C2=A0 )
]#sudo -u enterprisedb pgbackrest --stanza=3DRepo --log-level-console=3Di= nfo stanza-create=C2=A0

Initially It complains= about another=C2=A0 pgbackrest running=C2=A0 and aborted the stanza-creati= on
=C2=A0second attempt=C2=A0 : Without complaining=C2=A0about=C2= =A0 anything=C2=A0 the stanza creaton successful=C2=A0 :)=C2=A0 =C2=A0I cou= ldn't understand why it complained about=C2=A0 another pgbackrest runni= ng in the first place ?
( before running stanza creation on DB se= rver,=C2=A0 I first tried the stanza creation on=C2=A0 RepoServer as=C2=A0 = =C2=A0]# sudo -u postgres pgbackrest --stanza=3DRepo --log-level-console=3D= info stanza-create



= On Repo server : ( postgres= user for Repo server, but no PG installed only user=C2=A0 postgres = is created for=C2=A0 backup purpose)

]# #sudo -u <= span style=3D"background-color:rgb(255,153,0)">postgres pgbackrest -= -stanza=3DRepo --log-level-console=3Dinfo stanza-create=C2=A0

But no success(on multiple stanza creation attempts)=C2=A0 = =C2=A0:=C2=A0 It always aborted with a message=C2=A0 another pgbackrest is = running ..


So=C2=A0 Only=C2=A0 =C2= =A0stanza creation has to=C2=A0 performed=C2=A0 either=C2=A0 on=C2=A0 DB Se= rver or RepoServe but not on both servers ?

Kindly= =C2=A0shed some light on this.=C2=A0

Thank you,
Krishane







--0000000000006938d10620cb2ba4--