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 1pIBhx-0000GC-7R for pgsql-general@arkaria.postgresql.org; Wed, 18 Jan 2023 16:54:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pIBhv-0006Bn-Am for pgsql-general@arkaria.postgresql.org; Wed, 18 Jan 2023 16:54:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIBhu-0006BW-VG for pgsql-general@lists.postgresql.org; Wed, 18 Jan 2023 16:54:39 +0000 Received: from mail-pg1-x534.google.com ([2607:f8b0:4864:20::534]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pIBhs-0004ts-R1 for pgsql-general@lists.postgresql.org; Wed, 18 Jan 2023 16:54:38 +0000 Received: by mail-pg1-x534.google.com with SMTP id s67so24956460pgs.3 for ; Wed, 18 Jan 2023 08:54:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=QKe4dmdqFrb3wZgEivTrQAKpw7eVf1IBIDFBEqb9MFc=; b=Dct/AqARr2yFZTwwa2Mh7bp8/uT/F9PMSziOqzEh7ReRj5EA+95QPGd9hLOmIV2s+m jrk5t3lA7BD58cEg8GAEbwLo+mdnRAxzmiDGU8EfxbeJ19ZYBNGZeS8ALeNoyWNgDkJZ fGKFKP4ae2VxLRTFuq4z8DSiYP7yUct8xaVfbFgkAGhSz22dduScE5cHY1JsnpchMmNc 2efbDpYrleOBzEyb0442APx+ogI5Z1hze3VeXg6rAp6E8GyG904/lX1yiDI/lsUlJUOU aDxHZjdLn+pdCLj9peucSBeVBM6G7FczOz/Sq7/pTx2PDWQXuQqQbjaI4jm79Tp4R8Jj tG+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=QKe4dmdqFrb3wZgEivTrQAKpw7eVf1IBIDFBEqb9MFc=; b=nR62Eehf4OOA7shkp66I1EN+hzm10/k/FT8YnRg0WZ0rkrn3aAfezym4ymr1q+C0vr RE8hwZl5tbYCsW1v8o/3jXr4FZh1y/PG3YYUzDpOfXPx9/NUwJawCCVaIsiOOxbFpKii KZqBxFK1pt+QPaFjpfkwlLJNNkx+2wvKvhCqGLnAWP88oWdj0Nj7cV7l4q571X7bZivZ p507MCOE7C3NMe7OLmj7DOwEBKjFa7FHDSSdugifdOmd/xdRVkkjn3ZnmkokIvNWMEqa MBwkmXpGad5lKL6MOzBVTAEsjIaHsvbn0Hupfu6vkRFk7GUn9KrChoR7X03Iu8xX26jD PwqA== X-Gm-Message-State: AFqh2kpo+DCfY37eide/EzD/RTACSEw17Cc9FUiXW5L+4fooqtVkVV7E pnEj4gIPH1syqZr6aNGaiARBKxX8w7M= X-Google-Smtp-Source: AMrXdXta0GCM+HZ8NxMdGRCnUvnvGk2VDyZsE6q3ZzYtq0mejAEHnri4QAzVc6hgF9ltWBAFEe+k5Q== X-Received: by 2002:a05:6a00:1887:b0:58c:b0a:e504 with SMTP id x7-20020a056a00188700b0058c0b0ae504mr10123965pfh.18.1674060874421; Wed, 18 Jan 2023 08:54:34 -0800 (PST) Received: from ?IPV6:2601:681:5a00:f790:f8dd:6a1e:2a9f:5845? ([2601:681:5a00:f790:f8dd:6a1e:2a9f:5845]) by smtp.gmail.com with ESMTPSA id z4-20020aa79484000000b005823b7da05asm7017806pfk.122.2023.01.18.08.54.33 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Jan 2023 08:54:33 -0800 (PST) Content-Type: multipart/alternative; boundary="------------jkthTsOAU60meAO0oLstUKph" Message-ID: <26bf6de1-4a05-54b1-13ea-ce8c56e79344@gmail.com> Date: Wed, 18 Jan 2023 09:54:32 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools? Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: From: Rob Sargent In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------jkthTsOAU60meAO0oLstUKph Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 1/18/23 09:38, HECTOR INGERTO wrote: > > I wanted to understand the underlying issue. > > I use ZFS snapshots instead of a “correct” backup because with only > two machines it allows me to have backups in the main machine and in > the secondary too that acts as hotspare at the same time. > > To accomplish the same I would need 3 nodes. The main, the replica > hotspare and the proper backup. > Isn't "proper backup" typically thought of as offsite reloadable file capture, hopefully relatively recent?  Disaster recovery, and all that. --------------jkthTsOAU60meAO0oLstUKph Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 1/18/23 09:38, HECTOR INGERTO wrote:

I wanted to understand the underlying issue.

 

I use ZFS snapshots instead of a “correct” backup because with only two machines it allows me to have backups in the main machine and in the secondary too that acts as hotspare at the same time.

 

To accomplish the same I would need 3 nodes. The main, the replica hotspare and the proper backup.


Isn't "proper backup" typically thought of as offsite reloadable file capture, hopefully relatively recent?  Disaster recovery, and all that.


--------------jkthTsOAU60meAO0oLstUKph--