• nfh@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    ·
    1 year ago

    Why not both? Alerting to find issues quickly, a bit of extra storage so you have more options available in case of an outage, and maybe some redundancy for good measure.

    • RupeThereItIs@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      ·
      1 year ago

      A system this critical is on a SAN, if you’re properly alerting adding a bit more storage space is a 5 minute task.

      It should also have a DR solution, yes.

      • Nightwatch Admin@feddit.nl
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        A system this critical is on a hypervisor with tight storage “because deduplication” (I’m not making this up).

        • RupeThereItIs@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          This is literally what I do for a living. Yes deduplication and thin provisioning.

          This is still a failure of monitoring or slow response to it.

          You keep your extra capacity handy on the storage array, not with some junk files on the filesystem.

          You also need to know how over provisioned you are and when you’re likely to run out of capacity… you know this from monitoring.

          Then when management fails to react promptly to your warnings. Shit like this happens.

          • Semi-Hemi-Demigod@kbin.social
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            Then when management fails to react promptly to your warnings. Shit like this happens.

            The important part is that you have your warnings in writing, and BCC them to a personal email so you can cover your ass