Selfhosted

62413 readers

158 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

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

submitted 2 years 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 1 year 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 1 year 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.