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 1pICDC-00036o-TJ for pgsql-general@arkaria.postgresql.org; Wed, 18 Jan 2023 17:26:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pICDB-00023D-QI for pgsql-general@arkaria.postgresql.org; Wed, 18 Jan 2023 17:26:57 +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 1pICDB-000234-EH for pgsql-general@lists.postgresql.org; Wed, 18 Jan 2023 17:26:57 +0000 Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pICD8-0005EA-F1 for pgsql-general@lists.postgresql.org; Wed, 18 Jan 2023 17:26:57 +0000 Received: by mail-oo1-xc2b.google.com with SMTP id h3-20020a4ac443000000b004fb2954e7c3so798433ooq.10 for ; Wed, 18 Jan 2023 09:26:54 -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=FiSop6Igo8qUxHj20jNBnEXDIBZBfiSkHQlEeMiXU9k=; b=A0IZtykJgcbD4uLRZHEDbmIQiPe/par++xAuN5rVbeRShdO2G4V9UKan85y2Fl4D+c 72oIEpmGx3v6GJ56dXqYo0fpjWL9ZGXEY75cYZsuIkuIZtS7Bdn6TTBaTLdQbsrW/YlW CJfOGKxGF+dkxf0Lh7HJSuKF+6MPeIjr/YeGrqJrQXWJTrFOw7BMzuKXnEPh+Lq4a7eL xgdITC1TailXRlME+1QzCCLQOH7DqwCOmi5VOJyrDgbi6Cg+3HPJRZaorlRg2H3oLSpC Gtes76GD0STemDOtOawORePh783YL9e8+eGBl9A3cGUPIspVIN4Lvct5Lm2Tf+p6twvv ud8w== 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=FiSop6Igo8qUxHj20jNBnEXDIBZBfiSkHQlEeMiXU9k=; b=i/y9uEQZN/Ks8G/cG9tFAxYdm+mdOMN8f3g5k0wtNGK/M57uYGBwPMwh7djjBLVcQC 9GwH5pbxflPw8uNDAaGXhrBMC0qvWpt4LG7uQkTnfUmRD3pPw25ZK79VeEAlPVSUiFVr HCRoQkzpxiJekmsT3e0nW8qGtgbR6G8MBJ25LU0T2HpL/U6NUJUMlml5PuALNyGDhKQp RFi3qSZWppGfkzWjlEqnh2k7wxE15rDcom/SA0MtxkI0GsjrW2q8dj9k+VWs2pJwFGge OzbxsWE6L84yFr9MyOKSOzatttOU0+JFHEnfSvhXzIUn0cc/s+Q8VGHa3rkUWeYUzMB+ zDqg== X-Gm-Message-State: AFqh2krRLvzN5V+IX/LXFuiF6oD27XRnku1YdXsAat44qPbNT+vhETYK o1queI9+DhFgwGESlxJpoDeHqEnz/lg= X-Google-Smtp-Source: AMrXdXt1rHbsxoY2Oy28F/q6bkkTeNszj1X5qgOMs4Yo5ril+x2zMilv6G3yziQAJKNx2ugfE1ukBw== X-Received: by 2002:a4a:c30b:0:b0:4f2:b11a:8020 with SMTP id c11-20020a4ac30b000000b004f2b11a8020mr3605163ooq.5.1674062812402; Wed, 18 Jan 2023 09:26:52 -0800 (PST) Received: from [192.168.1.66] (108-250-206-84.lightspeed.nworla.sbcglobal.net. [108.250.206.84]) by smtp.googlemail.com with ESMTPSA id q187-20020a4a4bc4000000b004a3c359fdaesm16867401ooa.30.2023.01.18.09.26.51 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Jan 2023 09:26:52 -0800 (PST) Content-Type: multipart/alternative; boundary="------------AAW0BV1YiJZaz3F60NO2scQ6" Message-ID: <6ce6bae1-07db-594e-d87e-fdc3126c738c@gmail.com> Date: Wed, 18 Jan 2023 11:26:51 -0600 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-US To: pgsql-general@lists.postgresql.org References: <26bf6de1-4a05-54b1-13ea-ce8c56e79344@gmail.com> From: Ron In-Reply-To: <26bf6de1-4a05-54b1-13ea-ce8c56e79344@gmail.com> 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. --------------AAW0BV1YiJZaz3F60NO2scQ6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 1/18/23 10:54, Rob Sargent wrote: > 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. That is in fact what "proper backup" means.  "Hot spare" means high availability, and *HA is not DR*. -- Born in Arizona, moved to Babylonia. --------------AAW0BV1YiJZaz3F60NO2scQ6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 1/18/23 10:54, Rob Sargent wrote:
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.

That is in fact what "proper backup" means.  "Hot spare" means high availability, and HA is not DR.



--
Born in Arizona, moved to Babylonia.
--------------AAW0BV1YiJZaz3F60NO2scQ6--