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 1stZdD-00HU46-L5 for pgsql-general@arkaria.postgresql.org; Wed, 25 Sep 2024 21:33:08 +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 1stZdC-00EiMM-24 for pgsql-general@arkaria.postgresql.org; Wed, 25 Sep 2024 21:33:06 +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 1stZdB-00EiMD-Kt for pgsql-general@lists.postgresql.org; Wed, 25 Sep 2024 21:33:05 +0000 Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1stZd9-0013RZ-0t for pgsql-general@postgresql.org; Wed, 25 Sep 2024 21:33:04 +0000 Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2f761cfa5e6so3574811fa.0 for ; Wed, 25 Sep 2024 14:33:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727299981; x=1727904781; darn=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=aVk5CIHTphc+aG7tsre6P/YLsHZRaNwAfiK7OzZshHw=; b=SH5sJibh9KUYa/IBjO50yXVFY4YwGW7a1lp9uTVg89aaCju6k2FD1LuA57BFCjPT6M 1gRX0qsq59TRgcYVjq0+Z8IPFF1oP4POt3Ns+bijD8oKl4a7g0CVgosKcO8JtujtIXwk Gg6e2UokvBo/flKlx6PM4/Ef0QjTjhbWYQerXDuq6qxg5FGlyxL8tTcaN8GSEw+IYO8v m42Zf3pMflnhMbqVI4X05djld5wRQ9mexk9Ex8qitL1lHORTL4AFOOIOQio93NVOzVL3 B7nmcn60AGuIl7En12la86cyx5aASitASNeGFCpbaID8oS+9Eor2PffpJkDx1OIVfGFg king== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727299981; x=1727904781; 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=aVk5CIHTphc+aG7tsre6P/YLsHZRaNwAfiK7OzZshHw=; b=KMUVpuMTrA/7vbDUHR7hBdGw3bDTJrmIN1iBWVib5HeWr/RmuxgPiZN6Yug7LQGXxe un9XtrxGCRD7iQHK7N4pdDWu+ffVxb1I6SEerKvfmCHvNrsj6JdmxRoiLAQYxfSJYIO8 OU+MB7AvuEyIhq8/VFvPjR714VbJIiHRQMPH2oeZD3wpNeWzYduK8sBAX7mIQYm+98s0 nhRTkMdOl/SMdywsuLwMeIp0Nt1hcYMaupPUzmrPk0UaIB7ruJqZkMDhPjo//MXFWWRg hoeWrR+aRdguJMIuztoHx0nW9KNdUEXweNEAYeMGy2rsQHbNYZJR+S6/k9gsgrkJjdbl HZ+A== X-Gm-Message-State: AOJu0Yx3nEPZYeSUpxTtsKX1kSYw2/Put3napG1UJkocp/IbKC0M8Uws c7Bt3tMRICwEUaiUZuHF6Lv8aDIuqurg2Tkh3lapyc4Jwp7zrQmQg8dHG+zEDpWAPkOz2z9IBV0 uM1sH9LPtDVd+bC9+my1dV8b6P2M= X-Google-Smtp-Source: AGHT+IHmUMMUi8Rb1PirblylxUhV9WUmfkiuZLhjBvQGecSLagbPJf1mOFlWbYXbqWS8kZcZV805VrKLZ63e47Bpk2E= X-Received: by 2002:a05:651c:1541:b0:2f3:eeab:7f17 with SMTP id 38308e7fff4ca-2f91ca5dd39mr26268681fa.41.1727299980343; Wed, 25 Sep 2024 14:33:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Wed, 25 Sep 2024 17:32:23 -0400 Message-ID: Subject: Re: PgBackRest : Restore to a checkpoint shows further transactions To: KK CHN Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000bfc3680622f85d08" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bfc3680622f85d08 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Sep 25, 2024 at 2:13=E2=80=AFAM KK CHN wrote: > PgBackRest : I tried to restore the latest backup taken at my RepoServer > to a testing EPAS server freshly deployed . > ... > Now I comment out the archive command in the test EPAS server > postgresql.conf and started the EPAS server. > * To disable archiving, you can pass --archive-mode=3Doff to pgbackrest in the restore command. Actually, for safety, you should always use this argument when restoring. * Please say "Postgres" not "EPAS" * The restore starts from your incremental backup, but then it will replay WAL created after that backup. Check out the postgresql.auto.conf file. * I think what you are looking for is --type=3Dimmediate * For debugging and helping to learn, it can be useful to use --pg1-path=3D/tmp/restoretest to restore to a different data directory. Jus= t remember to change the port. And always use --archive-mode=3Doff :) See specifically this section of the docs: https://pgbackrest.org/command.html#command-restore Cheers, Greg --000000000000bfc3680622f85d08 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Sep 25, 2024 at 2:13=E2=80=AFAM K= K CHN <kkchn.in@gmail.com> = wrote:
PgBackRest :=C2=A0 I tried to resto= re the latest backup taken at my RepoServer to a=C2=A0 testing EPAS server = freshly deployed .
...=C2=A0
Now I=C2=A0 comment out the archi= ve command in the test EPAS server postgresql.conf=C2=A0 and started the EP= AS server.

* To disa= ble archiving, you can pass --archive-mode=3Doff to pgbackrest in the resto= re command. Actually, for safety, you should always use this argument when = restoring.

* Please say "Postgres" not &= quot;EPAS"

* The restore starts from your inc= remental backup, but then it will replay WAL=C2=A0created after that backup= . Check out the postgresql.auto.conf file.

* I thi= nk what you are looking for is --type=3Dimmediate

= * For debugging and helping to learn, it can be useful to use --pg1-path=3D= /tmp/restoretest to restore to a different data directory. Just remember to= change the port. And always use --archive-mode=3Doff :)

See specifically this section of the docs: https://pgbackrest.org/command.html#= command-restore

Cheers,
Greg

--000000000000bfc3680622f85d08--