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 1sXF1W-002eZs-1D for pgsql-general@arkaria.postgresql.org; Fri, 26 Jul 2024 07:05:54 +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 1sXF1U-00730n-GQ for pgsql-general@arkaria.postgresql.org; Fri, 26 Jul 2024 07:05:52 +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.94.2) (envelope-from ) id 1sXF1U-00730f-0r for pgsql-general@lists.postgresql.org; Fri, 26 Jul 2024 07:05:52 +0000 Received: from mail-vk1-xa32.google.com ([2607:f8b0:4864:20::a32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sXF1R-001VHW-8f for pgsql-general@lists.postgresql.org; Fri, 26 Jul 2024 07:05:50 +0000 Received: by mail-vk1-xa32.google.com with SMTP id 71dfb90a1353d-4f6be9d13cdso131714e0c.3 for ; Fri, 26 Jul 2024 00:05:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721977548; x=1722582348; 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=sagT7hpuPRFGzBvJMEhga2YFSPS9USulScX7CTmSpqc=; b=b+0RnvTIYuqJUFgN+Dvu4IP8TeXc4gXBzdTdeYSoyflIZu1bTBxbESlmGCA3O9y/8U BS36JAYVu7R1911oTetQ9BhFnWDWBJ76TPtSl3EM4eTFXo94hSNt+F1fLC75dqsHRaIC jy4/kSDzbFXvRMShPYiNyOudlQWwn+D4vkmh9csqgZYryAyNs4vamSo1xPAL4zSa/Xyb xFIJ6G2yyzFPskJMWObLqvnzU7bUe+YYuRP701ZYqCs6yi6TyRNv5x3Ac9axaHWNy7ZZ 5XiK1Ov/1HLD6TnSWEMkKckrBqkRYUOWk8wnLgsefTNobuEd4N9SSRp7nVQr14zMIDav z7Dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721977548; x=1722582348; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sagT7hpuPRFGzBvJMEhga2YFSPS9USulScX7CTmSpqc=; b=Vv56LTgPD5kcwvrLQ2KR1ZtUs/yT/Qn2lzC1nLUdHJxSEE2jlSQE2hWCYg3QkC7/+x f37Puhe+iPIYwYQlTSecAmy7KUgn7GRNBj4rgn2RlJ/wxDJjDmqxQ3t11uoI95J2czMP EW/Oi5Mb1A9+NpG+si0wqAY78U03pupelF3DGwRZ2oaTr1pgHDqYgKD05QkQbG1/Kq2y jBQNcg3Vvw6ARM+b5iEK9IWzpcw/0gbVT9NI+hsx3+gQ52e5BVxr43CTcjBtNEZlq14L CniGuj4UIcVAIFUu/EkAeqUDxtLoETtaWWiwHPVHT13ivVtN2VWPjWYRdWdivdIczvIk skZg== X-Gm-Message-State: AOJu0YzQP4yBkrkHiffHyGxtR52gvbi23F+gRopYrJ9VeLtchyvU6gy/ UiaDaPkexPkbWFCmDLliY9eSpipisBCgwGmQ+ThZulbKiKFc+U5bUUTG/2/YM3r+pnY6kHLhl/K qzDaagKh4/K2wjZuPcv/yIIZJd/c= X-Google-Smtp-Source: AGHT+IHYcieyfpnVWIzT9nS9FE8rDdnrev2hOfiCp/MXUVADZH5FURXAgB1frXThQoiBhOUoLQILs8S0dPpz98cOEoM= X-Received: by 2002:a05:6122:1d13:b0:4f2:ec14:3b6 with SMTP id 71dfb90a1353d-4f6c5bac961mr6594297e0c.6.1721977548234; Fri, 26 Jul 2024 00:05:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kashif Zeeshan Date: Fri, 26 Jul 2024 12:05:41 +0500 Message-ID: Subject: Re: pgBackRest for multiple production servers To: KK CHN Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000012e9f6061e21242c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000012e9f6061e21242c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi On Mon, Jul 22, 2024 at 9:35=E2=80=AFAM KK CHN wrote: > Hi list , > > I am exploring the PgBackRest tool for production deployment. ( My lab > setup with one Database server and another Reposerver deployed working > fine as in the official docs) > > Query: > > What may be the standard practice employed to backup multiple production > servers to one RepoServer ? ( the pgbackrest configuration on the > RepoServer part ) > > Is this the right way to achieve this (Defining multiple stanzas > Server1, Server 2 .. Server N and single [global] with repo1, repo2 > and repon N declarations ? > > Please correct me if I am wrong .. > Yes , normally there is one repo server which contains the configuration of all DB Servers in form of stanzas. Regards Kashif Zeeshan > > Thank you > Krishane > > > Please find the proposed pgbackrest.conf in the RepoServer for > backing up multiple database servers. > > /etc/pgbackrest/pgbackrest.conf on RepoServer > ################################################## > [ Server _1] > pg1-host=3D10.20.20.6 > pg1-host-user=3D pgbackUser > pg1-path=3D/var/lib/pgsql/16/data > . . . . . . . . . . . . . . . . . . . . . . . . . > . . . . . . . . . . . . . . . . . . . . > . . . . . . . . . . . . . . . .. .. . .. . . . . > > [ Server _N] > pgN-host=3D10.20.20.N > pgN-host-user=3D pgbackUser > pgN-path=3D/var/lib/pgsql/16/data > > > [global] > repo1-path=3D/var/lib/ Server_1_Backup > repo1-retention-full=3D2 > repo1-cipher-type=3Daes-256-cbc > > repo1-cipher-pass=3D0oahu5f5dvH7eD4TI1eBEl8Vpn14hWEmgLGuXgpUHo9R2VQKCw6Sm= 99FnOfHBY > process-max=3D5 > log-level-console=3Dinfo > log-level-file=3Ddebug > start-fast=3Dy > delta=3Dy > repo1-block=3Dy > repo1-bundle=3Dy > > repo2-path=3D/var/lib/ Server_2_Backup > repo2-retention-full=3D2 > repo2-cipher-type=3Daes-256-cbc > > repo2-cipher-pass=3D0oahu5f5dvH7eD4TI1eBEl8Vpn14hWEmgLGuXgpUHo9R2VQKCw6Sm= 99FnOfHBY > process-max=3D5 > log-level-console=3Dinfo > log-level-file=3Ddebug > start-fast=3Dy > delta=3Dy > repo2-block=3Dy > repo2-bundle=3Dy > > . . . . . . . . . . . . . . . . . . . . . . . . > . . > . . . . . . . . . . . . . . . . . . . . . . . . > . . > . . . . . . . . . . . . . . . . . . . . . . . . > . . > > repoN-path=3D/var/lib Server_N_Backup > repoN-retention-full=3D2 > repoN-cipher-type=3Daes-256-cbc > > repoN-cipher-pass=3D0oahu5f5dvH7eD4TI1eBEl8Vpn14hWEmgLGuXgpUHo9R2VQKCw6Sm= 99FnOfHBY > process-max=3D5 > log-level-console=3Dinfo > log-level-file=3Ddebug > start-fast=3Dy > delta=3Dy > repoN-block=3Dy > repoN-bundle=3Dy > > > [global:archive-push] > compress-level=3D3 > ################################################################### > > --00000000000012e9f6061e21242c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Mon, Jul 22, 2024 at 9:35=E2=80=AFAM KK CHN <= kkchn.in@gmail.com> wrote:
=
Hi= list ,=C2=A0

I am exploring the=C2=A0 PgBackRest tool f= or production deployment. ( My lab setup with one=C2=A0 =C2=A0Database serv= er and another Reposerver deployed working fine as in the official docs)
=C2=A0
Query:=C2=A0

What may be = the standard practice employed to=C2=A0 backup multiple production servers = to one RepoServer ? ( the pgbackrest configuration on the RepoServer part )=

Is this the=C2=A0 right way to achieve this (Defi= ning multiple=C2=A0stanzas=C2=A0 Server1,=C2=A0 Server=C2=A0 2 ..=C2=A0 Server=C2=A0 N and single=C2=A0 [global] with=C2=A0 repo1, repo2 and repon = N=C2=A0 declarations=C2=A0 =C2=A0?

Please corr= ect me if I am wrong ..

Yes , n= ormally there is one repo server which contains the configuration of all DB= Servers in form of stanzas.

Regards
Kas= hif Zeeshan=C2=A0

Thank you=C2=A0
Krishane
=


Please find the proposed=C2=A0 =C2=A0pgb= ackrest.conf=C2=A0 =C2=A0in the=C2=A0 RepoServer=C2=A0 for backing up multi= ple database servers.

/etc/pgbackrest/pgbackrest.c= onf=C2=A0 =C2=A0on=C2=A0 RepoServer
#############################= #####################
[ Server=C2=A0 _1]
pg1-host=3D10.20.20.6
pg1-host-user=3D pgback= User
pg1-path=3D/var/lib/pgsql/16/data
. . . . .=C2=A0 . .= .=C2=A0 . . . . . . . . . . . . . . . . .=C2=A0=C2=A0
. . . . . = . .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .= =C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0=C2=A0
. . . . . . . . . .= =C2=A0 . . . . . .. .. . .. . . . .

[ Server=C2=A0 _N]
pgN-host=3D10.20.20.N
pgN-host-user=3D pgbackUser
pgN-path=3D/var/lib/pgsql/16/data


[global]
repo1-path=3D/var/lib/ Server_1_Backup
repo1-retention-full=3D2
repo1-cipher-type=3Daes-256-= cbc
repo1-cipher-pass=3D0oahu5f5dvH7eD4TI1eBEl8Vpn14hWEmgLGuXgpUHo9R2VQK= Cw6Sm99FnOfHBY
process-max=3D5
log-level-console=3Dinfo
log-level-= file=3Ddebug
start-fast=3Dy
delta=3Dy
repo1-block=3Dy
repo1-bun= dle=3Dy

repo2-path=3D/var/lib/ Server_2_Backup
repo2-retention-full=3D2
repo2-cipher-type=3Da= es-256-cbc
repo2-cipher-pass=3D0oahu5f5dvH7eD4TI1eBEl8Vpn14hWEmgLGuXgpUH= o9R2VQKCw6Sm99FnOfHBY
process-max=3D5
log-level-console=3Dinfo
log= -level-file=3Ddebug
start-fast=3Dy
delta=3Dy
repo2-block=3Dy
re= po2-bundle=3Dy

.=C2=A0 =C2=A0.=C2=A0 =C2=A0.= =C2=A0 =C2=A0.=C2=A0 . .=C2=A0 .=C2=A0 .=C2=A0 =C2=A0.=C2=A0 .=C2=A0 .=C2= =A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 . .=C2=A0 .=C2= =A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 =C2=A0 =C2=A0=C2=A0
.= =C2=A0 =C2=A0.=C2=A0 =C2=A0.=C2=A0 =C2=A0.=C2=A0 . .=C2=A0 .=C2=A0 .=C2=A0 = =C2=A0.=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2= =A0 .=C2=A0 . .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0
.=C2=A0 =C2=A0.=C2=A0 =C2=A0.=C2=A0 =C2=A0.=C2=A0 . .=C2=A0 .=C2= =A0 .=C2=A0 =C2=A0.=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .= =C2=A0 .=C2=A0 .=C2=A0 . .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .=C2=A0 .= =C2=A0

repoN-path=3D/var/lib Server_N_Backup
repoN-retention-full=3D2
repoN-cipher-type=3Da= es-256-cbc
repoN-cipher-pass=3D0oahu5f5dvH7eD4TI1eBEl8Vpn14hWEmgLGuXgpUH= o9R2VQKCw6Sm99FnOfHBY
process-max=3D5
log-level-console=3Dinfo
log= -level-file=3Ddebug
start-fast=3Dy
delta=3Dy
repoN-block=3Dy
re= poN-bundle=3Dy


[global:archiv= e-push]
compress-level=3D3
###############################= ####################################

--00000000000012e9f6061e21242c--