Is it bad to keep my host machines to be on for like 3 months? With no down time?

What is the recommend? What do you do?

  • horse-boy1@alien.topB
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I had one Linux server that was up for over 500 days. It would have been up longer but I was organizing some cables and accidentally unplugged it.

    Where I worked as a developer we had Sun Solaris servers as desktops to do my dev work on. I would just leave it on even during the weekends and vacations, it also had our backup webserver on it so we just let to run 100%. One day the sys admin said you may want to reboot your computer, it’s been over 600 days. 😆 I guess he didn’t have to reboot after patching all that time and I didn’t have any issues with it.

  • R_X_R@alien.topB
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Prod environments typically don’t have downtime. Save for patching every quarter that requires a host reboot.

  • Brilliant_Sound_5565@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Never really shit my mini pcs down, sometimes I restart a proxmox node if I want it to use an updated kernal but that’s it. I don’t run large servers at home

  • CameronDev@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I boot my big server whenever i need it, everything else is 24/7. I have had no catastrophic failures in either for the last 2-3 years, so it seems to be fine?

  • TheStoicSlab@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I set up a cron job to reboot once a day. Its for my security cameras and I want to ensure access. But, if you dont have issues, you dont need to.

  • MrDrMrs@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I mean, so far the longest uptime I’ve seen at my current job is 9 years. Yes, that host should be patched. But given its role, and network access, it’s fine. Running strong. It is in a DC. Server grade hardware is designed with 24/7 operation in mind. Consumer hardware might be fine, but wasn’t designed with 24/7 critical operation in mind.

    At home, I have some nucs on 24/7, and a r740 and nx3230 on 24/7. The rest is for true lab env and I only power on as needed.

  • hauntedyew@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Even though live kernel patching is a thing, I generally do a full reboot every month or two for the next big patch.

    Full shut downs? Are we upgrading them, dusting them, or doing any other maintenance to them? That would be the only case besides UPS failure or power outage.

  • Deckdestroyerz@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    What are you guys even running that needs to be on?

    I just got a Dell R510 and a HPe Proliant 360 g7, installed esx on them, but i cant find anything that would justify running them for 24/7.

    I mean, besides a nas that holds some files… i cant find anything worthy… can only think about enterprise purposes which i dont meed at home.

    So, to answer the question, they are always off untill i want to experiment

  • Sylogz@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Only shut down for maintenance if hardware breaks. Otherwise reboots are done to update firmwares, esxi.

  • smstnitc@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Most things stay up 24/7

    I have a couple machines I don’t currently use for anything so they’re powered off until needed.

  • bryansj@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    If it is a Windows 95 server then every three days. Format and reinstall once every three months.