DigitalDilemma

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

help-circle



  • I don’t think I can agree with that, and I’m a pretty agreeable chap.

    In the days when people actually cared about the html layout and readability, FP spammed everything hugely, and inserted a lot of terrible cruft. Inventing zillions of new <style> tags for everything, even when the user just wanted to italicise a word. Use a <i> tag? No! We’ll invent a whole new style class and embed it in the headers.

    A few years ago I rather stupidly agreed to take over hosting of a website for someone that was dying. It had been written with FP and it took me months to de-cruft it using a lot of regexp and scrifting. (Some 8,000 images and around 2000 .html files).





  • Other have answered the runtime and load question very well already.

    I have three other points.

    1. Batteries degrade over time. Over-speccing your UPS means more likelyhood that things will hold up in three years time as the capacity given is for new ones. Plus, not running your UPS at 100% capacity reduces its stress. Again, more reliable.

    2. You can get a much better quality UPS by buying a second hand one without batteries off ebay and replacing them yourself, typically for a fraction of the cost of buying new. Plus you know you have new batteries. UPS is something where quality genuinely matters. I’ve had to carry a cheap and badly made UPS out of an office whilst it was on fire, so now I spec more carefully. (And ensure they’re metal bodied!)

    3. Consider what you NEED to power. What sort of power cuts are you expecting? Does it matter if something goes down?

    I UPS my servers and my main desktop, but not my routers, nor my wifi or IOT things. My internet provider also goes out when there’s a cut (I’m on a mesh system so rely on neighbours, who will typically also be down) and I can’t do much without power anyway, but it keeps the disks spinning. We typically get very short automated outages here of less than 10s (yesterday was a bad day, we had 9 within 2 hours)




  • Whatever you use, don’t build it to a definitive target.

    From personal experience, which may not be universal: No matter how carefully you plan this, your needs will change sooner than you think. Expect to re-organise things things, make changes constantly, and occasionally deal with messes you made. We do this to tinker and play and experiment, and that creates mess.

    So design something you can change. Luckily, that is what racks are about anyway, but do stuff like having space behind it for an extra coil of cable, space between servers, a shelf or two for those annoying random things, ability to extend. Space around it to work and move (don’t fix it to a wall in such a way that you can’t reach it all - wheels are good together with enough cable flex to be able to easily pull the rack out so it doesn’t go Whoo… as everything suddenly powers down)

    Obviously some rules are hard-baked, like “heavy stuff at the bottom”, but be fluid.






  • You’re welcome.

    Yes, you can create a list of files that takes little space, in linux that’s just “tree” to produce a list of directories and files (I don’t know about Windows, sorry)

    But only you can answer what you need to back up. If you judge the effort to re-download this data is more than the effort of backing it up (especially if you’re on a slow link), then backing it up makes more sense. Everyone has their own appetite for risk and their own shape of what they can spend in both time and money in sorting this. The important thing is that you’re thinking about it before you need it, that’s good!


  • A pet subject of mine.

    Firstly - sit down and consider what you need to backup.

    • Tier 1 - unique data. Stuff you created that doesn’t exist elsewhere.
    • Tier 2 - Stuff that would take a few days to repeat. Local configs, etc.
    • Tier 3 - Stuff you can just download again. (Steam library, media etc)

    Don’t backup Tier 3. I’m betting the size of data you need to back up shrinks a lot.

    Secondly - automate it. If there’s anything manual, then you’ll eventually stop doing it. Automate, automate, automate - and throw in some manual or automated checks of the backups to verify they’re actually usable.

    Thirdly - airgap it if you can, and if there’s much Tier 1 data. Offline disks. This gives you some protection against ransomware. Consider the risks and how to protect yourself. Obviously media failure, accidental deletion and ransomware, but also consider theft and fire. Do you really want your backups in the same location? Do they need encryption?

    I wrote quite a long blog on the subject if you’re interested in more.