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 1t1HZ2-00FWET-Mv for pgsql-general@arkaria.postgresql.org; Thu, 17 Oct 2024 03:52:40 +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 1t1HZ1-00FO8o-2f for pgsql-general@arkaria.postgresql.org; Thu, 17 Oct 2024 03:52:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t1HZ0-00FO8W-OA for pgsql-general@lists.postgresql.org; Thu, 17 Oct 2024 03:52:39 +0000 Received: from mail-pf1-x429.google.com ([2607:f8b0:4864:20::429]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t1HYy-001SzV-BX for pgsql-general@lists.postgresql.org; Thu, 17 Oct 2024 03:52:38 +0000 Received: by mail-pf1-x429.google.com with SMTP id d2e1a72fcca58-71e579abb99so319710b3a.2 for ; Wed, 16 Oct 2024 20:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bitnine-net.20230601.gappssmtp.com; s=20230601; t=1729137154; x=1729741954; 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=opTQPcMBAWiWWm+RAtgKOUpmdv0IuZpN2y018xAVY3M=; b=TPM8MkRyhLIUIvHoXrQAgJkYkopjKhrUDtjx1w/7OVQ6TNLeQ3b+IyTKAYnZN5stGT 81MUNTgPxaHqwtxMXzPgm+i5nSmaUXIB8wnVXHKE6TU2Na1D/iStMyhEmKhWOkLTycOL +Dnn9SzNrEYZ3cl+TQIZJClnGzxJpLOJKlpSvh3IGajc1qPZA8mFFRmsuZkDfSWx4EpG nktSlKM1t4uNmElCzUbVAvhZrxlxOBTxMaYLzj1Nh7PgTKUm6x/+3TkN9fn4rDctOPpE lWMEB9Kyk05XKjb8HN82M1W6k+V6CAWHs6/MyUFqBy/3r6jEn7M9OLkOaS3SDWh4hbTI zUNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729137154; x=1729741954; 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=opTQPcMBAWiWWm+RAtgKOUpmdv0IuZpN2y018xAVY3M=; b=XnWvOV1Va7faWEwN1rYeZgcPBcUZunMT2MYIegV2i5SQVMa2Aq4s9UfmSYXI0ZY+Il xKp3MOLjOP7I3SlF1UHuwzgBRIBoON7TTAOqAzO4jI2bwfB9hT5posDMSeRNE28iOnp3 VTNhJo4mmEm34hZ3w9YIIi/WXZNajfj1GIPYY2GkRtUdVbA+z4I2GtJ2N1B8g5OO9MjV O8JOi21YEA+E28yDZ0wF5xTIBCFOgMnzgwgmVVnapEA7+oWPRSdAEEzi/WOlygjZ8QN/ pTHRMMULbNUgR+itRVU+gZQNbhOxRYipPYLNQtEeZLA9CXzxvaoNj14zz2FqKtRdJj1U A7zA== X-Gm-Message-State: AOJu0YxwKi5GN6BMLHZV0kJcAWbqq+I6zGafp79kiaQsqCD5InwdnY8K EbKneQb0vJaGcqekkO+8oO6V/pJcM0HktSdqEbtgbEFiEm7S68VclWPXOxyzjOdjxnfKjs4WAMZ EgLJ9r+r/7H+yFj5BmrWjuAvt8Nul5IyT2KXo+W2xDUQ0iUYCWXY= X-Google-Smtp-Source: AGHT+IGPaogQlIU8YqTTQw5NM0BcW0DcFJqsS8qIj0XV4690RKtV9CbQ787YEAlZ01kXxS+iofkeoTyFugz8jRWPzwc= X-Received: by 2002:a05:6a00:91ce:b0:71e:55e2:2c54 with SMTP id d2e1a72fcca58-71e7da37396mr8180630b3a.12.1729137154205; Wed, 16 Oct 2024 20:52:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Usman Khan Date: Thu, 17 Oct 2024 08:52:22 +0500 Message-ID: Subject: Re: Backup To: Andy Hartman Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000d8498e0624a41d41" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d8498e0624a41d41 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, you can refer the following link where many backup methods are mentioned according to your need. Backups in PostgreSQL. In PostgreSQL, different types of=E2=80=A6 | by Usma= n Khan | Aug, 2024 | Medium On Thu, 17 Oct 2024 at 00:37, Andy Hartman wrote: > I am very new to Postgres and have always worked in the mssql world. I'm > looking for suggestions on DB backups. I currently have a DB used to stor= e > Historical information that has images it's currently around 100gig. > > I'm looking to take a monthly backup as I archive a month of data at a > time. I am looking for it to be compressed and have a machine that has > multiple cpu's and ample memory. > > Suggestions on things I can try ? > I did a pg_dump using these parms > --format=3Dt --blobs lobarch > > it ran my device out of storage: > > pg_dump: error: could not write to output file: No space left on device > > I have 150gig free on my backup drive... can obviously add more > > looking for the quickest and smallest backup file output... > > Thanks again for help\suggestions > > --000000000000d8498e0624a41d41 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
you can refer the following link where= many backup methods are mentioned according to your need.

= Backups in PostgreSQL. In PostgreSQL, different types of=E2=80=A6 | by Usma= n Khan | Aug, 2024 | Medium


On Thu, 17 Oct 202= 4 at 00:37, Andy Hartman <har= tman60home@gmail.com> wrote:
I am= very new to Postgres and have always worked in the mssql world. I'm lo= oking for suggestions on DB backups. I currently have a DB used to store Hi= storical information that has images it's currently around 100gig.=C2= =A0

I'm looking to take a monthly backup as I archive a month of= data at a time. I am looking for it to be compressed and have a machine th= at has multiple=C2=A0cpu's=C2=A0and ample memory.

Suggestions o= n things I can try ?=C2=A0=C2=A0
I did a pg_dump using these parm= s
--format=3Dt --blobs lobarch

it ran my device out of storage:
pg_dump: error: could not write to output file: No space left on devi= ce

I have 150gig free on my backup drive... can obviously=C2=A0add m= ore

looking for the quickest and smallest backup file output...
<= br>Thanks again for help\suggestions=C2=A0

--000000000000d8498e0624a41d41--