Selfhosted

46304 readers

639 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Backups made easy: btrfs + snapper + snapborg (totikom.github.io)

submitted 2 weeks ago by totikom@lemmy.ml to c/selfhosted@lemmy.world

18 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] totikom@lemmy.ml 3 points 2 weeks ago (1 children)

I guess we disagree about the point of backups then.

We just use different threat models.)

For me, the main threat is disk failure, so I want to get new disk, restore system from backup and continue as if nothing happened.

Surely, if your hardware or OS configuration changes, you should not backup /usr, /etc and other folders.

However, the proposed workflow could be adapted to both scenarios: a single snapborg config backs up snapshots from a single subvolume, so I, actually, use two configs: one for /home excluding /home/.home_unbacked and another one for / excluding /var and some other directories. This two configs have different backup schedule and different retention policies, so in case of hardware/OS change, I'll just restore only /home backup without restoring /.

[–] sugar_in_your_tea@sh.itjust.works 3 points 2 weeks ago

Makes sense.

I'm more interested in cutting off-site backup costs, so my NAS has RAID mirror to reduce chance of total failure, and offsite backup only stores important data. I don't even backup the bulk of it (ripped movies and whatnot), just the important data.

Restore from backup looks like this for my NAS:

Install OS + podman
Restore data from backup
Build and deploy containers from config

Personal devices are similar, but installing packages is manual (perhaps I'll backup my explicitly stored package list or something to speed it up a little). Setup takes longer than your method, but I think it's worth the reduced storage costs since I've never actually needed to do it and a few hours of downtime is totally fine for me.