155

I have a home server that I’m using and hosting files on it. I’m worried about it breaking and loosing access to the files. So what method do you use to backup everything?

(page 3) 15 comments
sorted by: hot top controversial new old
[-] Lnklnx 1 points 1 year ago

I use restic to back up to both local and remote.

The bigger question that almost nobody mentioned is how often you test your backups. I test monthly, because a backup you cannot restore is no backup at all.

[-] krdo@lmmy.net 1 points 1 year ago

I backup using a simple rsync script to a Hetzner storage box.

[-] bp99@lemmy.bp99.eu 1 points 1 year ago

It’s kind of broken at the moment, but I have set up duplicity to create encrypted backups to Bacblaze B2 buckets.

Of course the proper way would be to back up to at least 2 more locations. Perhaps a local NAS for starters. Also could be configured in duplicity.

[-] mosjek@lemmy.world 0 points 1 year ago

My server uses zfs, which allows me to create regular snapshots with sanoid. This makes it extremly easy to quickly recover individual services or vms without consuming a lot of disk space. In case the server is not recoverable, I still send the incremental snapshots to a pi clone with a large hard drive. If you use the native disk encryption, the snapshot can be sent encrypted without the second server having access to the data.This solution with zfs and sanoid/syncoid has often made my life easier and, in my experience, uses less bandwidth and cpu load.

[-] rambos@lemmy.world 0 points 1 year ago
  • kopia backup to 2nd disk
  • kopia backup to B2 cloud
  • duplicaty backup to google drive (only most important folder <1GB)

Most of the files are actually nextcloud so I get one more copy of files (not backup) on PC by syncing with nextcloud app

load more comments
view more: ‹ prev next ›
this post was submitted on 04 Jul 2023
155 points (98.7% liked)

Selfhosted

40443 readers
519 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS