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 1vg3l3-007iqt-1A for pgsql-general@arkaria.postgresql.org; Wed, 14 Jan 2026 16:30:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vg3l2-00BYGy-1u for pgsql-general@arkaria.postgresql.org; Wed, 14 Jan 2026 16:30:08 +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 1vg3l2-00BYGj-0q for pgsql-general@lists.postgresql.org; Wed, 14 Jan 2026 16:30:08 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vg3kz-000PkE-33 for pgsql-general@lists.postgresql.org; Wed, 14 Jan 2026 16:30:07 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-3f13043e2fdso3312007fac.1 for ; Wed, 14 Jan 2026 08:30:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768408206; x=1769013006; darn=lists.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=KnmFjNltq34z3qo2wfQB5rJV/XdoWSHwwvB8AaRi+do=; b=f6TadpMBEZj6P/wcpiDQ5/NXeCoTqQSMMRE1nhfmwF9E/oOeCchXAo8yTTQ7/Qjndt aYWBQRVFFwbhP19YrNBo28SN3cJVOlRBD2FmeHu2ffmUJXaFlAWEH9JN5z9V8YbXpoor sBFKoCqy9jPZSA/BbCYSKVhV5wqpSf4dY5crY++6TQ/yXVV0cxTFDXD65L1MqRYLefKy 8FaGq5DJCFKOFkf9zDiNhgBEMFG8HQFn2my5EFMXBCG/EEE6IramVwk/gS2yQXfyMNju +zoV8cKlCVE13pEu9Ram4FbdLK0+oFD5fhykZSwTDcWpofqwH1Nr0M7BmyjfeevdGvL3 HhoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768408206; x=1769013006; h=cc: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=KnmFjNltq34z3qo2wfQB5rJV/XdoWSHwwvB8AaRi+do=; b=crZhAoxbRiteyf96HM4b9ub3wQ2SUuuOx+D2oN92o/52r12d1oku/1XPr8CSbmDU7d Vyfp2cy/ArCfWMu5iN6B2V6Qx0owqa4mjiedp1CC/mT6NEYUK97MLkjrRNPc/6Kydrvs MASv8iBqb4kLZSWlAqqAoFQoyBw9jZUnSqw2U8jGDYZVRVo1FGwkr3WhofWO5Sel7VtD aV0XDWLxAt+BTFOIbE4zfg28MciA6VYYOGHGmFKO+LZ0njrTpixXLoY2nSXM+qocQXcR Uyn7s1tHeZMqNEvAnkHxxwxmEYuEu/PtRNDavx4lYhTfo9LtySEYIwPnuSc+GMfhfTNd s1Hg== X-Gm-Message-State: AOJu0Yw7e/ER9JvdJYiCqhrK8b0OXH4ctQtq+iMPWFI2aZFHzzuFd7E7 EJWpVa8Kdv39AIzq6taswdQXoufe3zjRqrnaNaL3OWYsFXDuqOkD81TWNMSg5zaTwyU75o7K2mg oDrKib9EH5U7dcuXXzRicPnoVmYXxeUMRUQ== X-Gm-Gg: AY/fxX7Ui1IWOJmamHOWiBqHtUyoezxKCyybiEsGnRRhww73oleAncSEDpuG3wsJuny X4vyoRMsyuGVLhwZCx+FA2Tz7BVjQw81PnaNDenBSgpAiF8hSXXEYQqM9t0fSTpTXW7PQz2pXZ6 e/QbKQx/zqbtntEgMKWpaJUyj55qbEkLDbxxTERAwYQZ9ZUelGRnDmiAVaxdW1aJZNsbxI0Zs5w rZ/BytSY0B+hYp1a18fglnhPjNyatCoDZXN9/qPOfpX8q7wkwoslcbt7oUSwaR4TeU8U3BEQBoZ 05Gy1TkCI7R6AuPsZ/nro+FOhmW4 X-Received: by 2002:a05:6820:c00c:b0:65c:f869:134a with SMTP id 006d021491bc7-66102df37c6mr1413630eaf.67.1768408204984; Wed, 14 Jan 2026 08:30:04 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Wed, 14 Jan 2026 11:29:29 -0500 X-Gm-Features: AZwV_Qh5dRRXMUsixsdEx98Pp_K-ezdlZFFyI5tXdEhPM2klJQO8OEnC7hb16Es Message-ID: Subject: Re: Move pgBackrest repo? To: "Colin 't Hart" Cc: PostgreSQL General Content-Type: multipart/alternative; boundary="000000000000e04d5706485b9e29" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e04d5706485b9e29 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: > > What is the best way to move a pgBackrest repo? > * rsync to get things mostly copied * use 'pgbackrest stop' to prevent it from running * verify no pgbackrest processes still going * update the conf file to point to the new dir * final rsync * rename the old repo dir so nothing writes to it by accident * use 'pgbackrest start' Cheers, Greg -- Crunchy Data - https://www.crunchydata.com Enterprise Postgres Software Products & Tech Support --000000000000e04d5706485b9e29 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:
<= br>
What is the best way to move a pgBackrest repo?

=
* rsync to get things mostly copied
* use &= #39;pgbackrest stop' to prevent it from running
* verify no p= gbackrest processes still going
* update the conf file to point t= o the new dir
* final rsync
* rename the old repo dir s= o nothing writes to it by accident
* use 'pgbackrest start= 9;

Cheers,
Greg

--
Enterprise Postgres S= oftware Products & Tech Support

--000000000000e04d5706485b9e29--