Verify your backups are working.
Before making any changes to your server database and system, be sure that you have to take a backup before doing any update and your backups are working fine. Make certain that you have selected the right backup and right location.
Check disk usage.
Keep your disk storage clean and don’t use your server system as an archival system. Delete old emails, logs and s/w versions that are not in use. A smaller data footprint means faster recovery. Keep an eye on your disk usages if your partition reaches 100 percent, you server may stop working and database tables and data may be corrupt and lost.
Monitor RAID Alarms.
Monitor your RAID status; all servers should use RAID. A single disk failure can cause a complete system failure.
Update Your OS.
Always update your system if you are using Linux because such OS release frequently update and staying on top of these updates can be difficult. To overcome this problem, you can use automated patch management tools and have monitoring in place to alert when a system is out of date. If you are updating your server manually (or not at all), you may miss important security updates. If you cannot automate your updates, then create a schedule to update your system. This will prevent your system from hacks.
Update your Control Panel.
If you are using a hosting cpanel be sure to update it as well. This will make your system up to date and fix any known issue related to hosting.
Check application updates.
Update your web applications, if you are using CMS or any open source program for you web application especially popular programs like WordPress.
Check remote management tools.
Maintain your remote server via remote console, remote reboot and remote rescue mode these are essential tools for remote server management.
Check for hardware errors.
Hardware problems are common but create a big issue, so you may review the log for any hardware problems like disk read error, network failure.
Check server utilization.
Review your server’s disk, CPU, RAM and network utilization.
Review user accounts.
If you have had staff changes, client cancellations or other user changes, you will want to remove these users from your system. Storing old sites and users is both a security and legal risk.
Change any passwords every 6 to 12 months, especially if you have given out passwords to others for maintenance.
Check system security.
Periodically review your server’s security using a remote auditing tool such as Nessus.