From nobody Fri Aug 27 08:08:45 2021 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AE14E17942CD for ; Fri, 27 Aug 2021 08:08:54 +0000 (UTC) (envelope-from matt@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gwsmk3N5Tz4cWd for ; Fri, 27 Aug 2021 08:08:54 +0000 (UTC) (envelope-from matt@userve.net) Received: from dc.ad.unitron.net (owa.usd-group.com [217.196.1.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 1D3B8238450; Fri, 27 Aug 2021 09:08:46 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=uk1; t=1630051726; bh=gN3UqzYM2gVZyl5ypvqxazVfw1BdsnGSIHvXC7D2nXo=; h=From:To:Subject:Date:References:In-Reply-To; b=S8Bi1k7VY5E4JG0w3pMBGt39lB4V9RptLucNpbtNRhV+PUdh3bBWzZqdt2BX21z/X rgPoME8J/n+eo2tzFLjlDVQM02EnNGJO7d/kKOCASETvBbyFKkTIc9wYvquCHoR2rV +ot/gs/n346YdSRcmk9BGCJVHtCLOI7WGupF97M0= Received: from dc.ad.unitron.net (192.168.0.100) by dc.ad.unitron.net (192.168.0.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.858.5; Fri, 27 Aug 2021 09:08:45 +0100 Received: from dc.ad.unitron.net ([fe80::5f3:fd35:db1:9809]) by dc.ad.unitron.net ([fe80::5f3:fd35:db1:9809%6]) with mapi id 15.02.0858.002; Fri, 27 Aug 2021 09:08:45 +0100 From: Matt Churchyard To: joe mcguckin , freebsd-fs Subject: RE: Backups to disk Thread-Topic: Backups to disk Thread-Index: AQHXmtJXMI4mGsgSYEOUlrpwalSE6KuG/NVw Date: Fri, 27 Aug 2021 08:08:45 +0000 Message-ID: References: <13B8BFED-E1E0-4912-BD9E-6581C308FF25@via.net> In-Reply-To: <13B8BFED-E1E0-4912-BD9E-6581C308FF25@via.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.8] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 X-Rspamd-Queue-Id: 4Gwsmk3N5Tz4cWd X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Do you mean you created a second zfs pool? A pool can contain multiple file= systems.=20 Judging by the command you give it looks like you have two pools called "ar= chive" and "backup", which by default will contain a single filesystem (dat= aset) with the same name, mounted on /{name}. If that's the exact command you used then the recv argument is wrong. It sh= ould be the dataset name, not a path. (i.e. drop the first slash if you wan= t the backup stored in a dataset called 08252021 on the backup pool) Personally, assuming you are backing up the primary dataset on the "archive= " pool, I would just do something like the following - zfs snapshot archive@08252021 zfs send archive@08252021 | zfs recv backup/archive Then the next day (as long as you still have the 08252021 snapshot) - zfs snapshot backup@08262021 zfs send -i 08252021 archive@08262021 | zfs recv backup/archive This will send only the changes, and you can always look through the snapsh= ots on the backup pool to see the list of snapshots and dates. Creating a b= ackup dataset using the date doesn't make a lot of sense, to me at least. A= fter this you can delete the 08252021 snapshot on the archive pool unless y= ou have any specific reason to want to keep it. If the backup pool was on a= separate system then it often makes sense to keep some snapshots so you ca= n easily recover files on the live system without having to pull them from = backup. If the backup pool is in the same system then there's not really an= y point. Matt -----Original Message----- From: owner-freebsd-fs@freebsd.org On Behalf= Of joe mcguckin Sent: 27 August 2021 00:29 To: freebsd-fs Subject: Backups to disk I created a second zfs filesystem to be used as backups. I made a snapshot = and tried zfs send archive@08252021 | zfs recv /backup/08252021. This fails with Freebsd complaining that zfs recv got a signal and aborted. Any thoughts? Thanks, Joe Joe McGuckin ViaNet Communications joe@via.net 650-207-0372 cell 650-213-1302 office 650-969-2124 fax