Operating system patches for known vulnerabilities must be implemented promptly. Disaster recovery drills: Perform restoration mock drills once a month (preferably, or quarterly if necessary) with the backup team to ensure the data can be restored in case of an issue.Incremental backups: Daily, Monday to Friday.The recommended backup criteria for production servers is: If you find any issues, coordinate with the storage and network teams immediately to correct them.Ĭommunicate with the backup team and provide them the data and client priorities for backup. Disk/SAN/NAS utilization: Check the I/O reports for externally attached storage to track and check the speed of read/write operations.Load average: If you're having performance issues, check the load average and tune the server for performance.Zombie processes degrade server performance, so find and kill any that exist. Zombie processes: Check for processes where the PID still exists in the process table after it is terminated.Memory utilization: Check memory utilization and clear the cache, if required.Parallely analyse the OS parameters like "Ulimits". If it is so, then coordinate with the application team to check it at application level and fine tune the same. to ensure that these are not consuming the CPU resources more than expected. CPU utilization: Consistently monitor and check the CPU utilization of the critical process like "java", "http", "mysql" etc.Running processes: Check for processes that are consuming more resources than expected, and take action to fine-tune the applications (with the help of the application team).
Maintain license counts and details for physical servers and virtual servers (VMs), including licenses for Windows, subscriptions for Linux OS, and the license limit of hypervisor host.