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 1t1rhg-000nG9-99 for pgsql-general@arkaria.postgresql.org; Fri, 18 Oct 2024 18:28:00 +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 1t1rhe-008bWH-Ed for pgsql-general@arkaria.postgresql.org; Fri, 18 Oct 2024 18:27:58 +0000 Received: from makus.postgresql.org ([72.32.157.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 1t1rhd-008bW6-W9 for pgsql-general@lists.postgresql.org; Fri, 18 Oct 2024 18:27:58 +0000 Received: from mail-yb1-xb2b.google.com ([2607:f8b0:4864:20::b2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t1rfQ-001a3p-U3 for pgsql-general@postgresql.org; Fri, 18 Oct 2024 18:25:46 +0000 Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-e290d48d3f7so2122634276.3 for ; Fri, 18 Oct 2024 11:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729275939; x=1729880739; 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=KEeyCN71hplSbVzB4fgQvKtK0NqlMslw5EmD3JeMrHs=; b=fB2y0IToNjzXov5/G3n2/F9uwhL6W5TQh4v8SAqFktIa1b997WwkiPFjCvMf2k3Rkr DxruCFOXr25F238ZH485rkQhotPG6K2lyQDKWeDS/hzqJKiESONhEx3tQ2AWaHJc4hJQ SxoEX2/0T0LqMHdGQqvIvNFEFZ66FxZdE+q+xDM14+5I21ci53ZtcQVV1uU2ihZuxFSb HYhrNU+oNOO3VPrD8IoIeYAcq+fGKiPrHg0S4U5p/5At6twLFHkhJgeBjwYV0tbYnh8R YqU/16xGC6RxecGdHUuNfFjh4+z/TDB+FoHwmRizHNpczvyS/6svEkM42qEievXbT72n F3GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729275939; x=1729880739; 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=KEeyCN71hplSbVzB4fgQvKtK0NqlMslw5EmD3JeMrHs=; b=VK3Fkryu22zUM/zCa1EMC3jvaU0Q47VqW0bkHuSWMnedZKo0itrjUgLtQ7Gj3+VV/C XsPh513zj6UdjMi6eOsm/unbSeE8hd8WEDkn3v+dZK4N+av3CjUX3OC1s3Gv4cNTFJd1 e5qWLYFmEAlsrlUPdo3xFBBhVXuqALbM/rYjZd4G2U7lEbikyeSyNNMb0gbTsKxGeUWS /uXZGHL2GaJfydla4iyUvZ+VopPFMx+Oy4O7lgLNJ29riGnG0sEK0InnhqcUppEQme82 k8X+SGbqppYkQfrxFqNlng8dkGupkJ5mnzdD2zzQJh+3elZoK0FR1xv8hmROSM64YLdi aBxw== X-Gm-Message-State: AOJu0Yy/5prRIUR889VY/LwP+1QL2nlZn4C+lr2Jjt+3KOf/aFjrvBDF Q7oUxvI0++GT8baXq+5Pu+sEUo41akBRyCxHsXd/69XMY3T5/Xp4jSLwwLrzw8PnLOXFFOw66Dt u/yR9eYNoGJqy9RsDtIJ7Nla9Q5Y= X-Google-Smtp-Source: AGHT+IHP/mwR/nbQVZAf8n/nViKXftZLQLGNE9xjiParLj/PI8alSkspOFxE1OaC20JcJURcEClBtCNYUK+t0lcsRbE= X-Received: by 2002:a05:6902:1a45:b0:e29:296d:782b with SMTP id 3f1490d57ef6-e2bb11c57abmr3280864276.8.1729275939358; Fri, 18 Oct 2024 11:25:39 -0700 (PDT) MIME-Version: 1.0 References: <1be444fc-e613-4489-aa19-b02ca16d4e30@aklaver.com> <17c9eeb9-f8a9-4ab3-b177-0c11dd345b6e@aklaver.com> In-Reply-To: <17c9eeb9-f8a9-4ab3-b177-0c11dd345b6e@aklaver.com> From: Andy Hartman Date: Fri, 18 Oct 2024 14:25:28 -0400 Message-ID: Subject: Re: Backup To: Adrian Klaver Cc: pgsql-general Content-Type: multipart/alternative; boundary="0000000000001592a60624c46ed1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001592a60624c46ed1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Windows Server 2022 I would like a backup process similar to what I'm used to using in the mssql world if that's possible with Postgres... I will be loading monthly archive data to Postgresql so that's why I probably only need once a backup .. once loaded data is just viewed thru an app... no updates.. in mssql you create the .bak and easily restorable .... that's what I'm looking for with Postgres thanks for replies.. On Fri, Oct 18, 2024 at 1:00=E2=80=AFPM Adrian Klaver wrote: > On 10/18/24 09:52, Andy Hartman wrote: > > Reply to list also > Ccing list. > > > Windows 22 and Postgres 16.4 > > > Is that Windows Server 2022 or Windows 10/11 with the 22H2 update? > > You also need to provide a more detailed description of what you want > the backup to do? > > > > > > > On Fri, Oct 18, 2024 at 12:04=E2=80=AFPM Adrian Klaver > > > wrote: > > > > On 10/18/24 05:39, Andy Hartman wrote: > > > I would like to use the closest thing to a mssql backup... > > > > > > > As in? > > > > Searching on 'mssql backup' returns a lot of choices. You will nee= d > to > > be more specific on what you want to achieve. Also be specific abou= t > > what versions of OS and Postgres you are using. > > > > -- > > Adrian Klaver > > adrian.klaver@aklaver.com > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --0000000000001592a60624c46ed1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Windows Server 2022

I would like a= backup process similar=C2=A0to what I'm used to using in the mssql wor= ld if that's=C2=A0=C2=A0possible with Postgres... I will be loading=C2= =A0monthly archive data to Postgresql so that's why I probably only nee= d once a backup .. once loaded data is just viewed thru an app... no update= s..

in mssql you create the .bak and easily=C2=A0restorable=C2=A0...= .=C2=A0 that's what I'm looking for with Postgres

thanks for= replies..



On Fri, Oct 18, 2024 at 1:00=E2=80=AFPM Adria= n Klaver <adrian.klaver@akl= aver.com> wrote:
On 10/18/24 09:52, Andy Hartman wrote:

Reply to list also
Ccing list.

> Windows 22 and Postgres 16.4
>
Is that Windows Server 2022 or Windows 10/11 with the 22H2 update?

You also need to provide a more detailed description of what you want
the backup to do?

>
>
> On Fri, Oct 18, 2024 at 12:04=E2=80=AFPM Adrian Klaver
> <adr= ian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0On 10/18/24 05:39, Andy Hartman wrote:
>=C2=A0 =C2=A0 =C2=A0 > I would like to use the closest thing to a ms= sql backup...
>=C2=A0 =C2=A0 =C2=A0 >
>
>=C2=A0 =C2=A0 =C2=A0As in?
>
>=C2=A0 =C2=A0 =C2=A0Searching on 'mssql backup' returns a=C2=A0= lot of choices. You will need to
>=C2=A0 =C2=A0 =C2=A0be more specific on what you want to achieve. Also = be specific about
>=C2=A0 =C2=A0 =C2=A0what versions of OS and Postgres you are using.
>
>=C2=A0 =C2=A0 =C2=A0--
>=C2=A0 =C2=A0 =C2=A0Adrian Klaver
>=C2=A0 =C2=A0 =C2=A0adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com><= br> >

--
Adrian Klaver
adrian.klave= r@aklaver.com

--0000000000001592a60624c46ed1--