On Tue, Sep 26, 2017 at 2:00 PM, Michael <[email protected]> wrote: > > Hmm. Diskutil info reports that it is backed by a sparse bundle. So the > system does track that, and time machine could see that. What I need is a > block device loopback device, and a way to feed that sparse bundle to that > block loopback, so it would look like it was on a block device instead of an > image file. > > Any idea how to do that?
lolwut!? But seriously, no idea. You could probably do something like that by implementing your own FUSE plugin, but I'd be surprised if anything like that exists. Sparsebundles are already mountable and I doubt many people are going to take the time to re-implement it. This is about the time that some pops in with a link to exactly such a working project. > The point of putting this file system in a sparse bundle was to make sure > that the next time it dies / needs to be recovered from an online backup > (backblaze) was to ensure that file meta-data is saved properly. At the same > time, I want to have a local history backup so that I don't have to worry > about downloading if I don't have to. (2/3rd of the disk is for time machine, > and 1/3rd is for this stuff). So, my reading is that you're backing up to a sparsebundle because that that will preserve the metadata you care about. I think I'd look instead at to another backup tool. In the wake of Crashplan shutting down their unlimited, multi-user plan, I've been evaluating Duplicacy backing up to B2. Duplicacy does handle some metadata, but it's not a perfect score in BackupBouncer. Duplicacy does handle multiple backup destinations (ie. local and cloud). Have you considered other tools? Arq is probably a good option for you here. -- arno s hautala /-| [email protected] pgp b2c9d448 _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
