How should I do backups? (sh.itjust.works)
submitted 2 years ago* (last edited 2 years ago) by 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
[–] 3 points 2 years ago (2 children)

How do you handle the cache invalidation issue with Borg when backing up multiple systems to one repo? For me if I access a Borg repository from multiple computers (and write from each) it has to rebuild the cache each time which can take a long time.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 2 years ago* (1 child)

    I seperate them by archive name prefix and never had the issue you describe.

    Edit: it seems I just never noticed it, but the docu suggest you're right. Now I am confused myself lol.

    https://borgbackup.readthedocs.io/en/stable/faq.html#can-i-backup-from-multiple-servers-into-a-single-repository

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 2 years ago

    Easy: I make a Borg repository not only for a single server but for each directory. In this way if I need a file from nextcloud with an extremely generic name like "config" I only search in there and not sift between 100k similarly named files

  • source
  • parent