Server Maintenance Checklist

You never know when disaster could strike; if you did, then there would be no disaster. Couple this with the fact that (whilst some argue on the specifics) data loss can be crippling to nay and all companies, and you have a major potential problem.

That's why we here at Process Street created this Server Maintenance Checklist.

By running through this bad boy every month (in combination with our other IT processes) you can ensure that your server remains in tip top condition whilst staying locked tight against security threats.

Let's get started!

To kick off our server maintenance checklist, you must first ensure that all details of the maintenance procedure (and the server itself) are recorded. Do this by utilizing the following form fields.

If you wish to record any extra information about the maintenance process or server, feel free to add more form fields!

First up, make sure that your backups are in working condition before making any changes to your production system.

You'll want to run some test recoveries if you are going to delete critical data. Remember to double check that you are saving to the correct backup location.

Next up, you need to check your server's disk usage. By this, we mean that you should be getting rid of any old or outdated software.

Think of it this way; your production system shouldn't double up as an archival system. By keeping your system free of old software, you can both reduce the strain on your server and limit the potential for security issues.

Now you need to perform some basic checks on your RAID alarms.

Check that your RAID’s error notification system is configured properly and functions as expected - this is especially important as most RAID levels tolerate only a single disk failure.

If you miss a RAID notification, a simple disk replacement could turn into a complete failure, so make sure that you thoroughly .

You also need to make sure that your server's OS is up-to-date by checking for (and implementing) system updates. Whilst doing this, it's also worth noting the OS in the form field below, for any required later reference.

Updates for Linux systems are released almost daily and many of these fix important security issues, so it is highly likely that Linux systems will need updating. Even if you regularly update your systems, be sure to check just in case.

If you do not have a management service or auto-updates enabled, be sure to also review your OS for any critical security updates.

Get on the mailing list for your OS so you know when critical security patches are released.

If you have a kernel update, you will need to reboot your server unless you use a tool like Ksplice.

Make sure to update your server (or hosting) control panel as well - this one's a double-whammy, as it also updates the software it controls.

Example:

With WHM/cPanel, you must manually update PHP versions to fix known issues. Simply updating the control panel does not also update the underlying Apache and PHP versions used by your OS.

After you have updated your server, make sure to review the web applications and update those as well. That's all there is to this step!

Next up in the server maintenance checklist, you need to check in on your remote management tools (if applicable). Use the sub-checklist below to tick off the tools as you check them.

If your server is co-located or with a dedicated server provider, check that your remote management tools work.

Remote console, remote reboot and rescue mode are the 3 essential tools for remote server management, but you can always edit the sub-checklist if you wish to regularly check more than those 3.

Now you need to review the logs for any signs of hardware problems. Record your findings using the form fields below.

Overheating notices, disk read errors, network failures could be early indicators of potential hardware failure, and so all must be noted and accounted for.

There's no point in updating everything on your server and making it watertight if the server itself can't handle the strain you're putting on it. Hence, it's time to review your server’s utilization.

Use the sub-checklist above to record which aspects of your server's utilization have been checked and the multi-line text field to record your comments.

Whether completely fine or dangerously overloaded, note down the status of each aspect in the comments box as you go. If you are nearing the limits, you may need to plan on adding resources to your server or migrating to a new one.

Now you need to review the user accounts on your server. Primarily, you should be looking for any old or outdated sites and users - record them in the form field below.

Storing old sites and users is both a security and legal risk. If you have had staff changes, client cancellations or other user changes, remove them from your system to help secure your server against unwanted entry.

You're almost there! The second-to-last step in the server maintenance checklist is to change the passwords on your server, if necessary. Whether necessary or not, however, record the date of the last password changes in the form field below.

Depending on when your passwords were last changed, this step may not be necessary. It's highly recommended to change passwords every 6 to 12 months, especially if you have given out passwords to others for maintenance purposes.

As we previously stated, though, you should always record the date of the last password change (be it today or 3 months ago). This will help to remind you of how long it has been since the last change, and when the next one is due.

Finally, you need to review the server’s security using a remote auditing tool such as Nessus. Record a copy of the scan results with the form field below.

Regular security audits serve as a check on system configuration, OS updates and other potential security risks, and so it's vital that this step is carried out. 

Reference: 10 immutable laws of security administration.

Congratualtions! You have completed the server maintenance checklist, and so can sit safe in the knowledge that your servers shouldn't be going down any time soon.

Sharon Fisher - On the Quest for the Mysterious Source of the ‘Data Loss Causes Company Failure’ Statistic

Jeff Huckaby - Selecting a Backup Location

Jack Wallen - Linux 101: Updating Your System

cPanel

Microsoft TechNet - Remote Server Administration Tools Overview

Tenable Network Security - Nessus Vulnerability Scanner

Jeff Huckaby - 10 Immutable Laws of Security Administration Revisited

Inventory Management Process

Network Security Management

Client Data Backup Best Practices

Computer Maintenance Guide

Server Setup Process

Virtual Private Server Setup

IT Support Process

Helpdesk Management

Server Security Checklist

Information Security Incident Response

SQL Server Audit Checklist