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.96) (envelope-from ) id 1vg36Y-007Zbq-2T for pgsql-general@arkaria.postgresql.org; Wed, 14 Jan 2026 15:48:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vg36Y-00BEc4-06 for pgsql-general@arkaria.postgresql.org; Wed, 14 Jan 2026 15:48:18 +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.96) (envelope-from ) id 1vg36X-00BEbv-2G for pgsql-general@lists.postgresql.org; Wed, 14 Jan 2026 15:48:17 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vg36V-000PPY-1x for pgsql-general@lists.postgresql.org; Wed, 14 Jan 2026 15:48:17 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-45a85a05a70so2108007b6e.3 for ; Wed, 14 Jan 2026 07:48:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768405695; x=1769010495; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=l/z6nNiUhY9fyX8M5Pf84vJ2UX38EFo3/40XGA8uLUc=; b=d9nRtBk2wkfndWyR1UOUAvLw418cMjPKz033Ie9I1zz0N4VSuLzUFJDR2/3iBt0Deu wHl16DQIma62iwxezOuuqv/UvzJQEUC9p+J/CIvUBNiX6v58tS0hn3od+IICvQs+SGRj +RlOlOV/CqVvgjEZzQ5ZY2IKNcBGliOfzp/XQJ8Pxt6UnQY5JF5SSsmn4SA9eP0R18ac U+dtPBaiQwfKhujNuF2HxxWI+KRWhJFdrWyboIzHyftWGTgDnoD60+c1EaWWBdlyl6Ky 1+kqn77n8UAuAJDEaCEUy3jnOB8oGVamy3lNvRiPcOa9qULJxac55IJj+x6SSmJHVDDq s8MQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768405695; x=1769010495; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=l/z6nNiUhY9fyX8M5Pf84vJ2UX38EFo3/40XGA8uLUc=; b=JMuHx70d9GILBhuCQfgSw0ACazbclC1Ru8Or9oWIcIXAgJX7+/bel7ZTG304rpDoB9 WseJD7rQEt2P2bwKdvmYF8JNj6PyB1jUyhIL5egOLJ52S2mNTb/ZdiWcr9BXd/hXtD0i XG/0WJU/+AN4/SW6zUrWJ+agLnr+g+Ra9sPuG2nk8uexy5qjv32G2lSmOUYo4tcYqWye YnPHCGBqaX7TKQQCQcXo7GiyJtbUCF2K9IlCQ4KcHTEDNmhXBWCe561ziNnHGx5qrCNN kPWDAd+XbQ/zmUG2PmHtRO48nQq1LyPF9kuleecPN009TGRXJfoCPLmNEMjAPMD718wp dTpA== X-Gm-Message-State: AOJu0Ywag3to0mYwYu05hHU5srLUPsuC7X8A/SeuMaHeYplI3OLUtJdK FcYQmfqG+MpB13XMZ/hgXIoLVwxywdkx0keaAg7ZUSe5MpUzP1Dut8emKEBGBK6ZVIK7rO+dZnZ 9JBe4HarDp9zZ30tRP8DAFvz/IX6Bjqdd2ZtH X-Gm-Gg: AY/fxX4axpKaxF9WITb8Z0WDWn+eTvbJ9zlWDbXAW0UcryRfmv0aBKYqnmFP0foWAYq nxEu5R77//NFD76vA5wOTeieiHsQArDXV5SlmE5RHm6wH7hbRxWb3cOnewoupigogF5T7Sbb0XV xsXr1Wo6d9xFcl/I4yVJtgNJvUXMYkxNEfjtIbcGc4YqDUwhJkEMmI0NhAzvqftqX42jvcH1Jzd OgjQZ53pGFyfVPiYEayDPQrmKg22wXv93Luoz+hTdtti+K6iNoEOZPcFmDALUzr41XYZTFGZ499 W8vJdme9BrLg6czD+f23q9HeMafamA== X-Received: by 2002:a05:6808:1692:b0:450:907:b523 with SMTP id 5614622812f47-45c73b3ba45mr1418804b6e.6.1768405695314; Wed, 14 Jan 2026 07:48:15 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 14 Jan 2026 10:48:04 -0500 X-Gm-Features: AZwV_QgL3Umagt8rAD5uYAQRhSDmjZ4xsipkuqVEDwsMgGQ_h7oJVZPcpXcv7bA Message-ID: Subject: Re: Move pgBackrest repo? To: PostgreSQL General Content-Type: multipart/alternative; boundary="00000000000049be8606485b0907" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000049be8606485b0907 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jan 14, 2026 at 10:24=E2=80=AFAM Colin 't Hart wrote: > Hi all, > > What is the best way to move a pgBackrest repo? > > It was configured as /var/lib/pgbackrest, but we want to move it to > /data/pbackrest to get it off the root partition. > > It is being written to continually by archivers from several servers. > Since access is over ssh, there's no server component that we can just st= op > for the duration. > The first thing I'd do is start rsyncing from /var/lib/pgbackrest to /data/pbackrest. I don't, though, know enough about remote PgBackRest configuration to know whether PG on the db servers needs to be stopped for the moment when you reconfigure pgbr on the repo server. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000049be8606485b0907 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jan 14, 2026 at 10:24=E2=80=AFAM = Colin 't Hart <colinthart@gm= ail.com> wrote:
H= i all,

What is the best way to move a pgBackrest r= epo?

It was configured as /var/lib/pgbackrest, but= we want to move it to /data/pbackrest=C2=A0to get it off the root partitio= n.

It is being written to continually by archivers= from several servers. Since access is over ssh, there's no server comp= onent that we can just stop for the duration.
=
The first thing I'd do is start rsyncing from /var/lib/p= gbackrest to /data/pbackrest.

I don't, though,= know enough about remote PgBackRest configuration to know whether PG on th= e db servers needs to be stopped for the moment when you reconfigure pgbr o= n the repo server.

--
Death to <Redacted>, and butter sauce.
Don't boil me= , I'm still alive.
<Redacted> lobster!
--00000000000049be8606485b0907--