Path: ...!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: vallor <vallor@cultnix.org>
Newsgroups: comp.os.linux.misc
Subject: Re: Time machine backups
Date: 8 Jan 2025 20:27:12 GMT
Lines: 39
Message-ID: <lu85d0Ffuq9U2@mid.individual.net>
References: <vkjmdg$30kff$1@dont-email.me> <vlhhes$1q4t2$2@dont-email.me>
	<RWYeP.56817$vfee.53192@fx45.iad> <vljb2o$27g6v$5@dont-email.me>
	<XHafP.16926$G93a.13818@fx05.iad> <vljkk3$29dna$3@dont-email.me>
	<kVcfP.505626$0O61.228231@fx15.iad> <vljqt8$2amtn$2@dont-email.me>
	<YoefP.510691$0O61.490083@fx15.iad> <vljsmi$2b457$1@dont-email.me>
	<lu5p8oF4lskU2@mid.individual.net>
	<slrnvnrpt7.2oheu.lars@cleo.beagle-ears.com> <vllp8c$2ouqc$4@dont-email.me>
	<slrnvnt3db.307lp.lars@cleo.beagle-ears.com> <vlmfup$2ta1j$1@dont-email.me>
	<vlmg4f$2r761$1@dont-email.me> <slrnvntk6j.31j9q.lars@cleo.beagle-ears.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net U8yrpr6rKHhLGbD9Zyh4TA3aa5BjVzN2yFAqewyGLSf6ZDIfhX
Cancel-Lock: sha1:Te8EwfP5oP/OoZ6N4FWhO9F0vnY= sha256:hkKkhInXur7GmhCUE1dYrGHWRM0QVnqJz9VmW0P5rVg=
X-Face: +McU)#<-H?9lTb(Th!zR`EpVrp<0)1p5CmPu.kOscy8LRp_\u`:tW;dxPo./(fCl
 CaKku`)]}.V/"6rISCIDP`
User-Agent: Pan/0.161 (Hmm2; c45f6052; Linux-6.12.8)
Bytes: 2996

On Wed, 8 Jan 2025 19:24:03 -0000 (UTC), Lars Poulsen
<lars@cleo.beagle-ears.com> wrote in
<slrnvntk6j.31j9q.lars@cleo.beagle-ears.com>:

> On Wed, 08 Jan 2025 18:25:29 +0000, Rich wrote:
>>> If you must use samba as the backing store, then use something like 
>>> Restic which stores the data in its own internal format and only 
>>> requires "basic file storage and basic filenames" support from the 
>>> underlying backing store.
>>> 
>>> Restic: https://restic.net/
> 
> On 2025-01-08, Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
>> Or tar(1), with or without compression.
> 
> I think restic has promise.
> 
> tar(1) does NOT allow me to have a complete backup for every snapshot
> without wasting space on multiple copies of the majority of files tht
> did not change.
> 
> I suppose one could use one large file on the samba server, mount it
> through some tunnel that lets you see it as a block device; create an
> ext4 file system on that block device, then use rsync to that file system
> to create a backup with versioning. Could this be done with a loopback
> mount?

I was going to suggest that, but also using LUKS to encrypt
the volume -- at least if you're storing it on some cloud provider.
"It should work." (More famous last words. ;)  )

(One downside is LUKS apparently won't allow a sparse file
being used for your loopback mount to remain sparse, since
it encrypts across the whole block device.)

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.12.8 Release: Mint 21.3 Mem: 258G
   "A pessimist is never disappointed."