I have a 56 TB local Unraid NAS that is parity protected against single drive failure, and while I think a single drive failing and being parity recovered covers data loss 95% of the time, I'm always concerned about two drives failing or a site-/system-wide disaster that takes out the whole NAS.

For other larger local hosters who are smarter and more prepared, what do you do? Do you sync it off site? How do you deal with cost and bandwidth needs if so? What other backup strategies do you use?

(Sorry if this standard scenario has been discussed - searching didn't turn up anything.)

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 8 months ago (1 child)

@NekoKoneko A second system in a secure local with minimal redundancy that can PULL backup data from your production environment at a rate fast enough to keep up. In my case, production is a many node Ceph cluster with flash storage and my backup is a single server loaded with big hard drives in a locked room at work (with approval). Both my house and work have fiber. The backup server pulls data from my production cluster on a regular basis using rsnapshot. It does use RAIDZ1 so I can run my hard drives until they fail without losing backups, but especially because it would take a massive amount of time to rebuild the backup server should I need to do so from scratch. If you have a large catalog of Linux ISOs downloaded via torrent, I might recommend keeping a (backed up) folder containing the old torrent files, that way you can just download them from the source again should you lose everything. Let the community be your backup on those.

  • source
  • hideshow 1 child comment
  • [–] [S] 1 point 8 months ago

    Thank you. I think the "folder of torrent files" you and others have said is probably a good failsafe anyway.

    I assume the pull requirement is to offload the process resource use as much as possible to the backup system?

  • source
  • parent