Hi there, I’ve been meaning to go get more serious about my data. I have minimal backups, and some stuff is not backed up at all. I’m begging for disaster.

Here’s what I’ve got: 2 8tb drives almost full in universal external enclosures A small formfactor PC as a server, with one 8tb drive connected. An unused raspberry pi. No knowledge of how to properly use zfs.

Here’s what I want: I’ve decided I don’t need raid. I don’t want the extra cost of drives or electricity, and I don’t need uptime. I just need backups. I want to use what drives I have, and an additional 16tb drive I’ll buy.

My thought was that I would replace the 8tb drive with a 16tb one, format it with zfs (primarily to avoid bit rot. I’ll need to learn how to check for this), then back it up across the two 8tb drives as a cold backup. Either as two separate drives somehow? Btrfs volume extension? Or a jbod connected to the raspberry pi, that I leave unplugged except for when it’s time to sync the new data?

Or do you have a similarly cheap solution that’s less janky?

I just want to back up my data, with an amount of rot protection, cheaply.

I understand that it might make sense to invest in something a bit more robust right now, and fill it with drives as needed.

But the thing I keep coming to is the cold backup. How can you keep cold backups over several hard drives, without an entire second server to do the work?

Thanks for listening to my rambling.

  • Droolio@feddit.uk
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 day ago

    You’re limiting yourself somewhat if you’re not able to plug in multiple drives at the same time. Otherwise, I might suggest mergerfs for basic JBOD. You won’t be able to use a single ZFS to avoid bit rot - only detect it. SnapRAID - ideal for offline setups - would be the next step up if you could dedicate one of your drives to parity.

    In your position, I’d do Duplicacy backups split/spanned over multiple backup drives (however you connect them).

    It has a pretty cool Erasure Coding feature that protects individual chunks from bit rot and possibly even bad sectors, plus the whole database-less architecture makes it very robust. De-duplication, high levels of compress, and encryption. Plus you can keep historic snapshots, so you can avoid the risk of accidentally sync’ing ransomware over the top.

    Edit: the CLI is free for personal use, and is source-available. Written in Go and extremely performant.