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 1v6ktM-009AZt-Qk for pgsql-general@arkaria.postgresql.org; Thu, 09 Oct 2025 07:16:48 +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 1v6ktK-000lIM-L4 for pgsql-general@arkaria.postgresql.org; Thu, 09 Oct 2025 07:16:47 +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 1v6ktK-000lI9-Ac for pgsql-general@lists.postgresql.org; Thu, 09 Oct 2025 07:16:47 +0000 Received: from mail-yx1-xb130.google.com ([2607:f8b0:4864:20::b130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v6ktJ-001BPX-10 for pgsql-general@postgresql.org; Thu, 09 Oct 2025 07:16:46 +0000 Received: by mail-yx1-xb130.google.com with SMTP id 956f58d0204a3-63b960a0a2bso743915d50.1 for ; Thu, 09 Oct 2025 00:16:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759994203; x=1760599003; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=lCwxJWS73ftTGztsFQT1muik/99yCmFQmjUFm+eBaMY=; b=I77cNpviP/WA+GdandDsy/n7Tt3Cj2tstp2nqLhkNS+t6+7YJz68lJhD3Xhg6ChMUX RyaxpEH7fczbtf+dkwMPu1lmoiwiKTZcBp20alWhw4TGryFJOdjZRIogH52qciiSPthC q1pNZrCUVf9cmqQC8eQqn4tbeDXaMm9l68GuR40pHE4RaYbdvULv2APnKrsERkM/i218 kca8nD55FQZVv91c94yEiLKyN+IB0rEuEGfg4hPTE172LdnBdG6FAsJi1IiHlzxAGzqT JT+ObyScp4duzbG0bOkfYRm+lApdeb0J3Wsmt0c7QJDzOqw8Lr4gd3Sv1Xfy1ab4muzw klaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759994203; x=1760599003; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=lCwxJWS73ftTGztsFQT1muik/99yCmFQmjUFm+eBaMY=; b=bfXCRnjoxRd6CGWsVaNDp5Se3U9JiJZFhDhqWsyq097+Lkp1qG5h4hbyaUWskOZeTq q97FGNFBe6BkRJJlefNUSmhLaGZkW7iWmbw+OOcFdftQ//mkysKWHHBiVBfkBeZFe4bP kkRWdI3YwSjWpDZkKxv17TgdM289c9Hw1hDEG+/KMwSq1DXY6iVnH57ZUvtIX2qRmiZO T+fkcjl+Ft6RkSEXp2REqPPW30WnrRBI+4PW7+NwPPT/tvFkucXxgb7Csmcz/j+WumjV 34YJu9M9iidCY7G5R9Pdxhq4Z860OS9HAOq5SRFTH+Qs8wmqlIRiB0L+YvbE/Ief7VNI eRxQ== X-Gm-Message-State: AOJu0YwVwmKWVFe3zHibhnWSc31OIgm7m2KuY1fe5KQezZeG6bVoiGB2 pYFgI1ncnofDcj0rsUUsYTKb6labYmyBwqVcO61FxdcquPEAl4z/pAA3iDqnyLzkKtZ9F2c5DG4 uke1Y4n8yToPN9jVckcRlk60dteIPg2+5SD8y X-Gm-Gg: ASbGncsEh8iYfyfWA49r6Ev5Cv7TM+kg9X3kx+fW9r7K66GtSKUoBjt12+o8xRzcWsy Y0DOOaDZUzmpFB7TtXTX31LvhLEBnQeIAUvehX3Rft+WUkeqQbXsBGYVC5HI33xfg8sdmqzDpNu opVxt2NkySm8makaK4OQ4ecRx141k+5+SW6GBWRbd+IjHgh7pctIG5yd/Jztcu9HyfNuQ3pSChF zbU/pIQiazkWYRjlQj9CnJ+4T/x/tfM X-Google-Smtp-Source: AGHT+IEOfEn2WGpbGlf8H+K0bR1NJenKEOJIZolYIW/C5dAILgNt4U0kEasbs8Np65u9aiMFAPSMnkTL4sE8jnwuVng= X-Received: by 2002:a53:b6cf:0:b0:63b:6b56:e6af with SMTP id 956f58d0204a3-63ccb8f3929mr4719334d50.36.1759994203431; Thu, 09 Oct 2025 00:16:43 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Thu, 9 Oct 2025 12:51:25 +0530 X-Gm-Features: AS18NWBczLH7NMrQuC1vn9EDDgpkWdeZ4fC9km3SYutZQsA7SOS7e2pQzr-xMps Message-ID: Subject: Pgbackrest changing RepoServer to new one To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000004d69cd0640b4959f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004d69cd0640b4959f Content-Type: text/plain; charset="UTF-8" List, I am in need of changing Repo Server of an existing working pgbackrest setup(RHEL 9.3 , pgbackrest 2.52.1 database version 16) *I have googled, got the information that I need to do * 1. First shutdown the Postgre Server cluster/instance. ( This is a production server, downtime permissions required if need to do so) 2 stop the stanza and delete the stanza 3. Then recreate the stanza with the same name from the new Repo Server. In need to change the RepoServer due to the storage limitations on the RepoServer forced to move to a large Repo Server. Can I bypass the step1 ( shutdown the postgreserver ?) and do step 2 and step 3, will this action stalemate the entire DB server and backup setup. Request your valuable guidance and advice. Thank you, Krishane --0000000000004d69cd0640b4959f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
List,

I am in need of changing Repo Ser= ver of an existing=C2=A0 working pgbackrest setup(RHEL 9.3=C2=A0 , pgbackre= st 2.52.1=C2=A0 database version 16)

I have goo= gled,=C2=A0 got the information=C2=A0 that I need to do=C2=A0

1. First shutdown the=C2=A0 =C2=A0Postgre Server cluster/in= stance. ( This is a production server, downtime permissions required if nee= d to do so)=C2=A0

2=C2=A0 stop the stanza=C2=A0 an= d delete the stanza=C2=A0

3. Then recreate the sta= nza with the same name from the new=C2=A0 Repo Server.

=
In need to change the RepoServer due to the storage limitations on the= RepoServer forced to move to a large Repo Server.
=C2=A0
Can I bypass the step1 ( shutdown=C2=A0the postgreserver ?) and do = step 2 and step 3,=C2=A0 will this action stalemate the entire DB server an= d backup setup.=C2=A0=C2=A0

Request your val= uable guidance and advice.

Thank you,
Kr= ishane
--0000000000004d69cd0640b4959f--