• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle



  • Generally speaking, fault protection schemes need only account for one fault at a time, unless you’re a really large business, or some other entity with extra-stringent data protection requirements.

    RAID protects against drive failure faults. Backups protect against drive failure faults as well, but also things like accidental deletions or overwrites of data.

    In order for RAID on backups to make sense, when you already have RAID on your main storage, you’d have to consider drive failures and other data loss to be likely to occur simultaneously. I.E. RAID on your backups only protects you from drive failure occurring WHILE you’re trying to restore a backup. Or maybe more generally, WHILE that backup is in use, say, if you have a legal requirement that you must keep a history of all your data for X years or something (I would argue data like this shouldn’t be classified as backups, though).








  • I know nothing about any of the other alternatives mentioned here, but I’ll pitch in my 2 cents that I am very happy with OMV. Haven’t had to touch it since they day I set it up, maybe 2 years ago. Except one time when I wanted to add a new SSH/FTP account for someone.

    In addition to the core file services, it supports running a Docker host, in which I have running instances of Portainer (a Docker Web UI), Transmission (a bittorrent client, woth VPN support, also with a Web UI), and Plex.



  • In my mind, it’s arisen as a result of two things about the JS ecosystem:

    A) JS doesn’t have a standard BCL, like most languages. It has the DOM API, for interacting with the browser, but it has almost no functionality baked in that is just there for the sake of it. There’s a few exceptions in more recent years, like Map and Set, but most menial tasks still involve rolling your own implementation, or pulling in a 3rd party one.

    B) Almost everyone places delivery size as the most-important concern in web apps, so that actively encourages (or at least, it used to, less so now that tree shaking is a big thing) developers to package things up at the tiniest possible granularity, in order to prevent applications being built with a ton of code that isn’t being used. Ironically, at scale, this effort had the exact opposite of the desired effect.