Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: "MichaelDBA@sqlexec.com" <michaeldba@sqlexec.com>
Mime-Version: 1.0 (1.0)
Subject: Re: PG_Base Backup take 8 to 9Hrs
Date: Tue, 8 Feb 2022 09:53:37 -0500
Message-Id: <9FC73308-0CB7-425A-8CD1-6750A4295E8A@sqlexec.com>
References: <20220208130225.kbecwy3oxvfi6iuk@jrouhaud>
Cc: Ram Pratap Maurya <ram.maurya@lavainternational.in>,
 pgsql-admin@lists.postgresql.org,
 Ashish Chugh <ashish.chugh@lavainternational.in>
In-Reply-To: <20220208130225.kbecwy3oxvfi6iuk@jrouhaud>
To: Julien Rouhaud <rjuju123@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/9FC73308-0CB7-425A-8CD1-6750A4295E8A%40sqlexec.com>
Precedence: bulk

Use pgbackrest instead

Sent from my iPhone

> On Feb 8, 2022, at 8:02 AM, Julien Rouhaud <rjuju123@gmail.com> wrote:
>=20
> =EF=BB=BFHi,
>=20
> Please don't try to recall messages sent on a mailing list.  That won't wo=
rk
> and will spam everyone.
>=20
>> On Tue, Feb 08, 2022 at 11:36:19AM +0000, Ram Pratap Maurya wrote:
>>=20
>> We are using Postgres -11 version and current PG DB size is 450 GB .
>>=20
>> Archive log enable in Database and we are running Full PG_Base backup and=
 it
>> will take 8 to 9 Hrs to complete the backup ,
>>=20
>> Please suggest  how to reduce the full DB backup time.
>=20
> That's ~16MB/s, so many times slower than a single old 7200RPM drive.  The=

> problem is likely not with postgres, you should get a better storage or a
> better network.
>=20
>=20