90
How should I do backups? (sh.itjust.works)
submitted 7 months ago* (last edited 7 months ago) by HumanPerson@sh.itjust.works to c/selfhosted@lemmy.world

I have a server running Debian with 24 TB of storage. I would ideally like to back up all of it, though much of it is torrents, so only the ones with low seeders really need backed up. I know about the 321 rule but it sounds like it would be expensive. What do you do for backups? Also if anyone uses tape drives for backups I am kinda curious about that potentially for offsite backups in a safe deposit box or something.

TLDR: title.

Edit: You have mentioned borg and rsync, and while borg looks good, I want to go with rsync as it seems to be more actively maintained. I would like to also have my backups encrypted, but rsync doesn't seem to have that built in. Does anyone know what to do for encrypted backups?

you are viewing a single comment's thread
view the rest of the comments
[-] bandwidthcrisis@lemmy.world 1 points 7 months ago

I can't recall storage costs (they're on the website somewhere but are not straightforward).

I was paying maybe $7 a month for a few hundred Gb, although not all of that was glacier.

But retrieval was a pain. There's no straightforward way to convert back from glacier for a lot of files and there's a delay. The process creates a non-glacier copy with a limited lifespan to retrieve.

Then the access costs were maybe $50 to move stuff out.

I moved to rsync.net for the convenience and simplicity. It even supported setting up rclone to access s3 directly. So I could do cloud-to-cloud to copy the files over.

this post was submitted on 30 Mar 2024
90 points (96.9% liked)

Selfhosted

40153 readers
372 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 1 year ago
MODERATORS