Reactive vs. Proactive?
The "we'll fix it when it breaks" approach may work for a while in small-scale environments; however, in enterprise infrastructure it is both costly and creates unpredictable business continuity risks. Proactive maintenance is a planned and documented process that prevents or anticipates failures before they occur.
Components of a Maintenance Schedule
A good IT maintenance schedule is divided into four time horizons:
- Daily: Automated monitoring checks, backup verification
- Weekly: Log review, disk space checks, update assessment
- Monthly: Patch application, security scanning, physical hardware inspection
- Annual: Capacity planning, hardware refresh assessment, DR exercise
Daily Maintenance Checklist
Daily checks that can and should be automated:
- Verify that backup jobs completed successfully without errors
- Confirm disk utilization is below threshold (warning: 85%, critical: 95%)
- Verify that critical services (web, database, email) are running
- Check UPS battery status and power monitoring alerts
- Review firewall and IPS alert summary
Automation tool recommendation: Zabbix or PRTG dashboards can be configured to send daily summary emails.
Weekly Maintenance Checklist
- Scan server event logs (Windows Event Log / syslog) for errors and warnings
- Clean up locked/expired accounts in Active Directory or Entra ID
- Evaluate pending updates in the patch management system
- Review VPN connection logs and failed authentication attempts
- Review CPU/memory usage trends for switches and routers
# Windows: Son 7 günün kritik olay kayıtları
Get-EventLog -LogName System -EntryType Error,Warning `
-Newest 200 -After (Get-Date).AddDays(-7) |
Select TimeGenerated, Source, EventID, Message |
Export-Csv C:\haftalik_eventlog.csv -NoTypeInformation
Monthly Maintenance Checklist
Patch Application
- Apply Windows Server and client patches via WSUS/SCCM/Intune
- Apply security patches to Linux servers (
apt upgrade/dnf upgrade --security) - Evaluate firmware updates for network devices (switch, router, firewall)
- Manage third-party application updates (Java, PDF reader, browser)
Security Scanning
# Nessus veya OpenVAS ile aylık zafiyet taraması
# Kritik ve yüksek bulgular bir hafta içinde giderilmeli
Physical Hardware Inspection
- Verify that server fans are spinning and operating normally
- Inspect cable management in the rack and tighten any loose connections
- Record server room temperature and humidity readings
- Run a UPS battery capacity test
Capacity Review
| Resource | Warning Threshold | Action |
|---|---|---|
| CPU (average) | > 70% sustained | Resource planning |
| RAM | > 85% sustained | Add memory / redistribute VMs |
| Disk | > 80% | Cleanup or expansion |
| Network bandwidth | > 70% sustained | Circuit upgrade |
Annual Maintenance and Planning
Hardware Lifecycle Assessment
| Component | Typical Expected Lifespan | Replacement Signal |
|---|---|---|
| Rack server | 5–7 years | Frequent failures, parts unavailable |
| NAS/storage | 4–6 years | Increasing disk error rate |
| Network switch | 7–10 years | EOL announced, security vulnerabilities |
| UPS | 4–6 years (battery: 3–5 years) | Battery test failure |
| Fiber/copper infrastructure | 15–20 years | Signal loss, high error rate |
License Renewal Schedule
Track the expiration dates of all software and hardware licenses in a spreadsheet:
- Operating system end-of-support (EOL) dates
- Security solution licenses
- Backup software subscriptions
- Network management licenses
Disaster Recovery Exercise
The annual full DR exercise should cover:
- Simulated failure of the production environment
- Measuring the backup recovery time (actual RTO)
- Testing DNS and network routing changes
- Post-exercise improvement report
Maintenance Documentation and Record Keeping
Every maintenance activity should be recorded:
- Date and time
- Person performing the maintenance
- Tasks performed
- Issues identified and action plan
- Next maintenance date
ITSM tools (Jira Service Management, Freshservice, ManageEngine ServiceDesk) allow you to keep these records in a structured format.
Conclusion
A proactive maintenance schedule is both a safeguard and a productivity tool for teams managing IT infrastructure. Regular and documented maintenance extends hardware lifespan, prevents unexpected failures, and demonstrates organizational readiness during audit processes. NRC Sistem provides planning for your IT maintenance schedule, maintenance services, and technical support processes under a managed services model.