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 1vJu4z-007YHJ-2C for pgsql-general@arkaria.postgresql.org; Fri, 14 Nov 2025 13:43:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vJu4x-006O6H-1T for pgsql-general@arkaria.postgresql.org; Fri, 14 Nov 2025 13:43:07 +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 1vJu4x-006O68-0N for pgsql-general@lists.postgresql.org; Fri, 14 Nov 2025 13:43:07 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vJu4o-0076ky-2M for pgsql-general@lists.postgresql.org; Fri, 14 Nov 2025 13:43:06 +0000 Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-450063be247so694775b6e.2 for ; Fri, 14 Nov 2025 05:42:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763127778; x=1763732578; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=pZ4+j32P6GQB54KbvOiOtyZzAuQX9/QMAOlEfDeBx+0=; b=aqmQNCuxBpcMkkdu8PhUtRwQ07MQqV49cem17CoOtVmCQik+s1cXj3t64HSlOvFve9 E1D1eawzy2y2WlbD0ozDdZuaS4Z+igmjm+/NpZhbKdbPG4Eh2iMrjzf0/a66xqmziCYu b9Zt64RnHN22MOyNjAxlCpdjlgvRwEjkw5vOaWsxR/BwSR6RcB+6GCMZA2BUNPFHsQN+ 13BVF4l0YncpzmebqAu7vcSPdEOo1h6+KeUTdSwyt/eN4uFIFgCxo8FvqJAno0kEg764 dsYh7SMjIO4pUzNhZF2GXTR+e3M0nmcFjW8WQPoYep0brulbTfM/RMKcCGcrEsJ7JA4I tFtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763127778; x=1763732578; h=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=pZ4+j32P6GQB54KbvOiOtyZzAuQX9/QMAOlEfDeBx+0=; b=YaFJwnBlcfi0FJQwNGgSmR7NM9JZWL5dNg2R88ls+hBKoufjq6Y3vLVPf+9LaT58cr sL6erF6xWN+HVR6qj1knFWKBDSF6WGXK5tL9u+AvWHv7bky8KwMlQwYWgLc0Tj86tVv3 12dA549kucY07qvWlUFRaCfnJRur3pX04C8YIUYKwA08IuOA1vjjLrPA474yB8jKyKFW lGD0fP7IYJSBGvVFurCQlQYZe2SIizqcpjweqJf1fgkfTHfJ2+51VRwfMnVTyw0Ea31j HrHUvfscwR9O9CxoGeSgxfBLhYxlbihthTau7CY1eKD5BQAIRZ0R0U1w3pKGLERK3077 8j3w== X-Gm-Message-State: AOJu0YzyhheczLpLRLeKzi9jhdhEAtlypU1RHZWIONk8DrqyIdYZ4MzO arzIXX5nTEsUiVVa8R8m9cMRyhlQZh5XYknxvoG/xTuZGcXHFcThTkWtudP0I58de8SRtpV2pz0 ZZ2r5hvyM6qoqwPyhL38oPvqT/8GABf++Wg== X-Gm-Gg: ASbGnctDv5P6C7uWL9uGzqN4a+rabfFHMgDAFgO0b0kvWjspr2WtMIWascaN9VEozHc n+EYACN5CQHj+DO/6v1iY0IMsEJtB4eWHeUsoCVd+x1yZ6EbGSig4Z8aacEN1VhagkIGbht5LSk OsGvmnJT5yRgCPIMhorgpoB0iYNZSrGZVI8IiuCA7pYWN1bd507cx8ErGVBgFYJsRAHq14Gq3dM DcDwGDBpDl9n4cx1mwzAAfmb8VWcQ6vrsA4EPdkdiBLMyDjc58AR0xhHnb0AZD66UwNO29F X-Google-Smtp-Source: AGHT+IGqFiZXn0tN1+tzXEpkvSpu0FuBvyYiedYgLwkJr9EJ5Ge5bEGCw+tVVO0wQNjStlojpLwszoA/I1sYi3kzASU= X-Received: by 2002:a05:6808:120c:b0:44f:e471:b52e with SMTP id 5614622812f47-45097451108mr1308855b6e.11.1763127777848; Fri, 14 Nov 2025 05:42:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Fri, 14 Nov 2025 08:42:46 -0500 X-Gm-Features: AWmQ_bkJ0uc97bePtNcjIip_ed3sU4iOOJSCZAI1EHB67UjhbIldv8YoOwm9gZs Message-ID: Subject: Re: Pgbackrest info output interpretation To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000e4722706438e2ccd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e4722706438e2ccd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Nov 14, 2025 at 3:27=E2=80=AFAM KK CHN wrote: > Hi, > > I am having confusion trying to understand the database size, backupsize > and repo backup size.. > > In my DB server I have du output as follows. > > /data/edb/as16 > [root@db1 as16]# du -h -d 1 > 5.3G ./data > 25G ./tablespace > 30G . > [root@db1 as16]# > > On my Repo Server pgbackest info says .... > > full backup: 20251114-121504F > timestamp start/stop: 2025-11-14 12:15:04+05:30 / 2025-11-14 > 12:20:58+05:30 > wal start/stop: 000000010000000500000024 / > 000000010000000500000024 > database size: 3GB, database backup size: 3GB > repo1: backup size: 431.0MB > > Could someone shed some light on 431 MB and database size:3GB, databas= e > backup size : 3GB compared to the DB cluster on disk usage output ? > > How to correlate the pgbackrest ( info) database size, database backup > size and repo1 backup size and actual du output on DB cluster. > Do you have the job log at "detail" level? That lists every file which is backed up. Sadly, no compression rates. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000e4722706438e2ccd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Nov 14, 2025 at 3:27=E2=80=AFAM K= K CHN <kkchn.in@gmail.com> = wrote:
Hi,=C2=A0 =C2=A0 =C2= =A0

I am having confusion trying to understand=C2=A0the = database size, backupsize and repo backup size..

I= n my DB server I have du output as follows.

/data/edb/as16[root@db1 as16]# du -h -d 1
5.3G =C2=A0 =C2=A0./data
25G =C2=A0 =C2= =A0 ./tablespace
30G =C2=A0 =C2=A0 .
[root@db1 as16]#

On my Repo Server pgbackest info says ....=C2=A0

full backup: 20251114-121504F
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 timestamp start/stop: 2025-11-14 12:15:04+05:30 / 2025-11-14 12:20:58+0= 5:30
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 wal start/stop: 000000010= 000000500000024 / 000000010000000500000024
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 database size: 3GB, database backup size: 3GB
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 repo1: backup size: 431.0MB

Could so= meone shed some light on=C2=A0 =C2=A0 431 MB and database size:3GB, databas= e backup size : 3GB=C2=A0 compared to the DB cluster on disk usage output ?=

How to correlate the pgbackrest ( info) database size, database bac= kup size and repo1 backup size =C2=A0 =C2=A0 and actual du output on DB clu= ster.=C2=A0
=C2=A0
Do you have the j= ob log at "detail" level?=C2=A0 That lists every file which is ba= cked up.=C2=A0 Sadly, no compression rates.

--
Death to <Redacted>, and butter sauc= e.
Don't boil me, I'm still alive.
<Redacted>= ; lobster!
--000000000000e4722706438e2ccd--