Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKIVy-00054r-RJ for pgsql-admin@arkaria.postgresql.org; Wed, 16 Feb 2022 11:30:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nKIVS-0005h8-0u for pgsql-admin@arkaria.postgresql.org; Wed, 16 Feb 2022 11:29:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKIVR-0005gz-My for pgsql-admin@lists.postgresql.org; Wed, 16 Feb 2022 11:29:57 +0000 Received: from mout.perfora.net ([74.208.4.194]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKIVO-0006IA-Mo for pgsql-admin@lists.postgresql.org; Wed, 16 Feb 2022 11:29:56 +0000 Received: from smtpclient.apple ([98.169.214.209]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0MQ4G5-1nPXhf1MW3-005IZM; Wed, 16 Feb 2022 12:29:48 +0100 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: "Michaeldba@sqlexec.com" Mime-Version: 1.0 (1.0) Subject: Re: Differential backup in database migration Date: Wed, 16 Feb 2022 06:29:47 -0500 Message-Id: <9AD73617-C013-4AF6-80C9-B7F1ECCE02A6@sqlexec.com> References: Cc: pgsql-admin@lists.postgresql.org In-Reply-To: To: Alex Balashov X-Mailer: iPad Mail (18F72) X-Provags-ID: V03:K1:mrWtQRfWrBNLhhI1SAEoHO/UHeqoV84qvOi896zJf1eqWKs1Fn9 EJxtK9rChMK5oDvG5lLAgpYx/x1UJkuUpsFebCrkzk8X0O/qWN4cv4xosYxcvi04ZLEViEQ yk/WfhyRuYr69QJEgGKqXHLeBv8ih64rbgL2+Nvkx++oJqRhMkF4ITFr31vnjXxP5vIi53y 6+yt7It4nWL5LkPFlHk7w== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:NZMgMoeHzzc=:VEpvaeHEVWt6s825ZVi/TM O99fRwS6Nl1cL66EygTil8EYD5PA1xrV4MgW/K+NjWN+snjJzpbBKHRnJ27VTu65gUFvLIFfz tao4unoayLVUxhJIf484jGOHMsXhZFXfEUdkl8N+0U5ZEd23+oOm3Pg1WpslU04mkdyxUukPF WTNrUuiLEMXVIVzQ34W0bcvOLgQej3JdwlmIVwDn/bqGDXnQ4OK5DawypWZQrUa70Eu9PPp4r fXd4q2kUgrFRbwHfRCk49kOauTD7gamygh4KQB/Ssw0Qj+M1v/0pSuaQgTyLEeYCkmQ8K/gZe OanDfXJ/Lgwx0SaDwxT+TwCNk7iDAH5CObBUmPB6nTGm0Ee7MYJFIvcxThKD3sNm67UKBoK7T QlmkDAFXBMP2e10hnUnlCK3tQCpgGpjqhEFDB/h9iAaFv7+pVs6gHRWyRRKbTG5sjv67CsGNu qY4Fa3QRBbWZKIvMh9wZCexE8jGO7Bs9+ExPAKAyRVA3co/xIPsQvTGxExhIWDXbOkSrvEU35 TVceF+PWRCwDflbwQF76YrLEDQSmzjTlwAkalp55hZAdfSLXPV6iOn+JOgA69N3h2d4WKj+wL yg+AmLXCN4BC9h6PQMz+hrwkcJNnsoD1c7iGY75JUXqDxqLZnSQeTe7RCuQnnvKGJtshSLsE6 Irpegfz9F+iSVYDerhyrB0cZwxUTaSvjgOIJf3igA49WG5kolJSXKT2UBlwcD6JeFVnxM3B1e ZM/gkIhsxfwEaj8q List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Consider pglogical with hardly any downtime and no need to catch any changes= during the cutover. Sent from my iPad > On Feb 16, 2022, at 6:24 AM, Alex Balashov wro= te: >=20 > =EF=BB=BFHi, >=20 > I sincerely apologise if this is a stupid question, in that it has been an= swered enough times to enter an FAQ canon: >=20 > I=E2=80=99m faced with the daunting prospect of upgrading a PG 9.6 install= ation to 14, in the process migrating a ~400 GB database. Due to the large j= ump in major versions, the on-disk block storage of course will not be in th= e slightest bit binary-compatible, so I will have to dump out the DB & impor= t it into the target DB, live via a network pipe. >=20 > This process is time-consuming, and can=E2=80=99t afford the downtime on t= he old 9.6 DB. The issue, of course, is that the 9.6 DB will change during t= he time this snapshot is being dumped out and imported. Ultimately, the targ= et database will need to be brought into consistency with the incumbent data= base (more or less) at the point of a cut-over. >=20 > I suppose the most intuitive solution to me would be to import the snapsho= t to the target DB, then take another, smaller differential backup of some k= ind, and in turn import that. But perhaps there=E2=80=99s another solution a= ltogether, i.e. a much faster backup & restore? I see that pgBackRest makes t= his argument to the prospective user. >=20 > I have no experience with pgBackRest or any such tool, so would appreciate= any advice on how to best go about this!=20 >=20 > Thank you in advance, and apologies again if the question is asked routine= ly. >=20 > =E2=80=94 Alex >=20 > --=20 > Alex Balashov | Principal | Evariste Systems LLC >=20 > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >=20 >=20 >=20