4 replies
by jcmoffitt Accepted solution
by Former member Accepted solution
by husnk3w02 Accepted solution
by cg it Accepted solution
"normally" note I said normally, you don't have to or should have to, reboot your servers unless required by updates, security patches, service packs,or application installation that requires one. If anything, there are blended threats that only initiate themselves when there is a reboot so putting servers on a reboot schedule can initiate a infection or security breach.
In the "old" days, admins rebooted servers to reclaim memory when there wasn't a lot of free physical memory. Since server performance is typically for background services and those services often have dependencies, the more services running the less free memory. Services don't automatically turn themselves off so over time, running services accumulate and this chews up resource, so admins rebooted servers to get rid of unnecessary background services and their dependencies.
Better course of action is to determine what services aren't actually needed to run on the server and disable them, thus freeing up physical memory and system resources.
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending