RedHat Systems under Systems Engineering Administration
We understand your RedHat Linux (RHEL) systems require the highest availability and can not be rebooted often due to the long jobs often running on your systems. To ensure proper security policies are updated and file systems checks are performed, there are three times each year all servers will be rebooted. This will take place during the following times we have found to impact the fewest people possible:
- The first week in January
- Spring Break
- The week after summer commencement
We will have automatic email reminders go out informing you of the exact date and time of the reboot several days before. We will also have staff available early every morning of the week of the reboots to ensure minimal downtime if something untoward happens during the reboot. All reboots will take place late at night, so that if a file system check is required it will complete by morning.
By having these maintenance schedules, we can ensure that your running system is patched appropriately for security matters and that your file systems are getting the proper file system checks (most filesystems require a check every 180 days). This should add to the overall stability and performance of your system(s).
Windows Systems under Systems Engineering Administration
We understand your Windows systems require the highest availability. To ensure proper security policies are updated each week, we have a maintenance schedule of Thursday morning 2 a.m. to 4 a.m. where reboots and other patching may occur. We can accommodate custom maintenance schedules on a per-customer basis as requested.
By having these maintenance schedules, we can ensure that your running system is patched appropriately for security matters and regular bug fixes. This should add to the overall stability and performance of your system(s).
