From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 543DD15815E for ; Thu, 8 Feb 2024 06:38:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4BBBF2BC021; Thu, 8 Feb 2024 06:38:08 +0000 (UTC) Received: from gw2.antarean.org (gw2.antarean.org [141.105.125.208]) by pigeon.gentoo.org (Postfix) with ESMTP id 78A8DE2A8B for ; Thu, 8 Feb 2024 06:38:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by gw2.antarean.org (Postfix) with ESMTP id 4TVnNt4c4sz8scJ for ; Thu, 8 Feb 2024 06:38:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at antarean.org Received: from gw2.antarean.org ([127.0.0.1]) by localhost (gw2.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MnQKKmj_zikS for ; Thu, 8 Feb 2024 06:38:06 +0000 (UTC) Received: from mailstore1.adm.antarean.org (localhost [127.0.0.1]) by gw2.antarean.org (Postfix) with ESMTP id 4TVnNt0zldz8sb4 for ; Thu, 8 Feb 2024 06:38:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mailstore1.adm.antarean.org (Postfix) with ESMTP id 4TVnNt0XqTz1H for ; Thu, 8 Feb 2024 06:38:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at antarean.org Received: from mailstore1.adm.antarean.org ([127.0.0.1]) by localhost (mailstore1.adm.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZEVSuHUsnK-9 for ; Thu, 8 Feb 2024 06:38:05 +0000 (UTC) Received: from iris.localnet (iris.adm.antarean.org [10.55.16.47]) by mailstore1.adm.antarean.org (Postfix) with ESMTPA id 4TVnNs4HmDz17 for ; Thu, 8 Feb 2024 06:38:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=antarean.org; s=default; t=1707374285; bh=jC87fFV9i0ueckkrYbhpJwE8oyAPKZ3syvgOYN67eEs=; h=From:To:Subject:Date:In-Reply-To:References; b=o0HWaLuHvmPfPbsd4PUG092PazS9CeXFiKRRQY5Chuhp+UYcJ2/ME7jXenOWQi4N6 iuvQ6W1o59i74os/mWOZ/clNTHoyuK7THmURFNpzwNkow8GlFNPlKkPWqh5ohTsF9J cfBLYkLCq7yFWRMApMYi28+B6c8NBjay4XVUXfq8= From: "J. Roeleveld" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Suggestions for backup scheme? Date: Thu, 08 Feb 2024 07:38:05 +0100 Message-ID: <4547854.LvFx2qVVIh@iris> In-Reply-To: <89a2a57b-761d-4cdf-b64c-7f876a37ef26@youngman.org.uk> References: <6028761.lOV4Wx5bFT@iris> <89a2a57b-761d-4cdf-b64c-7f876a37ef26@youngman.org.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 86a88cdf-7f99-49d7-95e7-ef4519c8aa85 X-Archives-Hash: e9a0895764a34392daeb12b7db2094d6 On Wednesday, February 7, 2024 10:50:07 PM CET Wols Lists wrote: > On 07/02/2024 11:07, J. Roeleveld wrote: > >> Because snapshotting uses so much less space? > >> > >> So much so that, for normal usage, I probably have no need to delete any > >> snapshots, for YEARS? > > > > My comment was based on using rsync to copy from the source to the backup > > filesystem. > > Well, that's EXACTLY what I'm doing too. NO DIFFERENCE. Actually, there > is a minor difference - because I'm using lvm, I'm also using rsync's > "overwrite in place" switch. In other words, it compares source and > destination *in*place*, and if any block has changed, it overwrites the > change, rather than creating a complete new copy. I must have missed that in the man-page last time I used rsync. Will have to recheck and update my notes just in case I need to use rsync again in the future. > Because lvm is COW, that means I have two copies of the file, in two > different snapshots, but inasmuch as the files are identical, there's > only one copy of the identical bits. > > >> Okay, space is not an expensive commodity, and you don't want too many > >> snapshots, simply because digging through all those snapshots would be a > >> nightmare, but personally I wouldn't use a crude rsync simply because I > >> prefer to be frugal in my use of resources. > > > > What is "too many"? > > I currently have about 1800 snapshots on my server. Do have a tool that > > ensures it doesn't get out of hand and will remove several over time. > > "Too many" is whatever you define it to be. I'm likely to hang on to my > /home snapshots for yonks. My / snapshots, on the other hand, I delete > anything more than a couple of months old. > > If I can store several years of /home snapshots without running out of > space, why shouldn't I? The problem, if I *am* running out of space, I'm > going to have to delete a *lot* of snapshots to make much difference... One of the things I didn't like about LVM was that it would have trouble dealing with a lot (100+, due to a bug in my script at the time) of snapshots. And having to manually (or using a script) increase the size given to these snapshots when a lot of changes are occuring. ZFS doesn't have this "max amount of changes", but will happily fill up the entire pool keeping all versions available. But it was easier to add zpool monitoring for this on ZFS then it was to add snapshot monitoring to LVM. I wonder, how do you deal with snapshots getting "full" on your system? -- Joost