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 1vIQvB-000ilF-2I for pgsql-general@arkaria.postgresql.org; Mon, 10 Nov 2025 12:22:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vIQv8-000EjE-2H for pgsql-general@arkaria.postgresql.org; Mon, 10 Nov 2025 12:22:54 +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.96) (envelope-from ) id 1vIQv8-000Ej1-1D for pgsql-general@lists.postgresql.org; Mon, 10 Nov 2025 12:22:54 +0000 Received: from mail-pl1-x62b.google.com ([2607:f8b0:4864:20::62b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vIQv6-006yhE-13 for pgsql-general@postgresql.org; Mon, 10 Nov 2025 12:22:54 +0000 Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-2957850c63bso29345205ad.0 for ; Mon, 10 Nov 2025 04:22:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762777370; x=1763382170; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=AbN1QQJzPpFtlMnOsSlAK9+nOlZKO+XDPqqAh7vuULA=; b=KTFvwyAUQHDSxW5rOVYTVn6yNb9tZi6tf8r2hY4lrK2d7WltmSejQiO/XUeh1wIutP N9EkGL2vUgnZLkvfwpDNcYVqIg1cPTOlfddwbBmfow2bLyRTB9cz7f0H4apn/nMu6M1X ktlMLu8z1pHvAnNRYMbCbrHKRkc4+nT8tt1cX+Y+FOr7UeFUEGKyu3aoaaHZ8oyG1+TU flQ9Pvp63+kMSpurXxMS7U3tFZlUAqtjdQI1kYKXQV1ENrwzVtU/Y8MNSFBbsdRh/cOQ 8Iyl894U46amvZqEMBMaDkTw46zw9SVt0bSIOL830KTFgtLEqcL1rQ2vQdTiel/kkDiq ZRGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762777370; x=1763382170; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=AbN1QQJzPpFtlMnOsSlAK9+nOlZKO+XDPqqAh7vuULA=; b=vEUvH6k1WCcxBUMRZk1Q3RCfPrFOSV9jEj1nhQwDkMu8difE2laribde9+comHeC+Z VeZw9wOYaRis7YgL7OKpyLBiK4fZFp5ZSIngqv2YCCdQcG4vY/667h28aY15R7ZQLkjx Pe0hXtoZTELCjIl3uF2zBW0VOGZtzILbnFMtuZiepgODfRuI1URj84eetMv3Mq4Uqpdf o/YgnO838/fqoG1Oj8j0sOoa1qD0UamJp0+fv7Wy9BwskxNP28OjLAkltWI+lp6MSUxS NL5Pqrbf4uHrrW3aCI94bQy2/8HurWG9efTnTqtKHqnjHyQZX4fb3BkFeoha9sWdRjpp D6EQ== X-Gm-Message-State: AOJu0Yzj/D2lXxpuQxRPfLzR5nRW2fG/IohDo4knmGKBAjK9AlsXEZ2M SFgiVyH++Yftds3DpnS0o/fKbywIzPTTxFtVsfpY9o1sLirfzbX5xoYYBapuaCFsVa9Wy3zBVf+ GZ3e8nuvWyiIcumbSyiI2hiwSGQZgxRvGQBmyfkM= X-Gm-Gg: ASbGnct6yBJbRPrGiZPjEEEoLQJHovIGnDdmzax88/JYurpy/lnRywcNU73vLgc/nO6 BweJX+zJL96KWF3E+uGEULDtIEqBb6ubVjkLxC/B3682jvJJO8W9y3x4bkycDvE1gzlZ7aCb1gd 8Sqe2rhzWaFSarX9OnlvZkHIX2qH6JcEHl1isPvk9TnuZYO/jep7H969S/DjIMIvH6NZPrWopB7 V7RJFRXw1ZvcPY1x9I4ecOmd2p7aoWkfqDG71F6kbXBShdgtUO6Ojo4eimHPTWE5pNGbaRKa1iV QxQ6BiwNNGDiBX4oOZGf4FWfNoM+aMca2r8YhJA= X-Google-Smtp-Source: AGHT+IHUrH+JFtpVgfStylzll6KSA4CE7LMZi4p//nZnWGxCb4QtcufNaeMGiDU0TOG3fiXTXcOhkw1ueUZUGyKw4Wc= X-Received: by 2002:a17:903:2441:b0:297:f527:885f with SMTP id d9443c01a7336-297f5278e1dmr83833595ad.0.1762777369997; Mon, 10 Nov 2025 04:22:49 -0800 (PST) MIME-Version: 1.0 From: Radu Radutiu Date: Mon, 10 Nov 2025 14:22:38 +0200 X-Gm-Features: AWmQ_bnWinYHM4q5eI4y4hsOm3lJeNhNmZrSxCtTelBm2oTh56cBsuGktpt6Y9Y Message-ID: Subject: Pgbackrest setup for two sites with limited bandwidth To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000f4f70e06433c9614" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f4f70e06433c9614 Content-Type: text/plain; charset="UTF-8" Hello, Is it possible to configure pgbackrest for a postgresql server pair using physical replication on two different sites with limited bandwidth (i.e. sufficient for data replication but not daily backups)? All tutorials and blogs describe a setup with either a single pgbackrest repo or multiple repos configured on the primary server. I am looking for a solution that has a second pgbackrest server on a secondary site that receives backups and WALs from the standby server in order to avoid most of the additional network traffic for backups/WALs. Is such a setup possible with pgbackrest or other PostgreSQL backups solutions? Best regards, Radu --000000000000f4f70e06433c9614 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

Is it pos= sible to configure pgbackrest for a postgresql server pair using physical r= eplication on two different sites with limited bandwidth (i.e. sufficient f= or data replication but not daily backups)? All tutorials and blogs describ= e a setup with either a single pgbackrest repo or multiple repos configured= on the primary server. I am looking for a solution that has a second pgbac= krest server on a secondary site that receives backups and WALs from the st= andby server in order to avoid most of the additional network traffic for b= ackups/WALs. Is such a setup possible with pgbackrest or other PostgreSQL b= ackups solutions?

Best regards,
<= div>Radu
--000000000000f4f70e06433c9614--