Geo SCADA Server Health: The Maintenance Checklist Most Operators Miss

Quick Answer

A comprehensive Geo SCADA server maintenance checklist covers database compaction and archiving, certificate and license renewal tracking, Windows Server patching, backup verification and restore testing, communication channel health checks, and performance baseline metrics. Most operators miss items beyond basic backup scheduling.

Database Maintenance

Database Compaction

The Geo SCADA SQL Server database grows continuously as historian data, alarm records, and audit logs accumulate. Without periodic maintenance, database fragmentation degrades query performance and increases backup times. SQL Server index maintenance should be scheduled weekly — either through SQL Server Maintenance Plans or a custom script that rebuilds fragmented indexes while the system is under low load.

Historian Archiving

Historian data retention policies should align with regulatory requirements and operational needs. TCEQ reporting typically requires 3-5 years of raw data. Beyond that, data can be archived to offline storage and removed from the active database. Review the Geo SCADA historian configuration annually to ensure retention periods are appropriate and archiving is functioning correctly.

Transaction Log Management

SQL Server transaction logs can grow to consume all available disk space if not managed. Verify that the database is in the correct recovery model (typically Simple for SCADA databases, unless point-in-time recovery is required). If using Full recovery model, ensure transaction log backups are scheduled and completing successfully.

Certificate and License Renewal Tracking

Geo SCADA uses SSL/TLS certificates for secure communication between servers and clients. Maintain a spreadsheet or calendar tracking:

• Geo SCADA server certificate expiration date
• WebX/Virtual ViewX web client certificate
• Mirror server replication certificate
• Any DNP3 Secure Authentication certificates
• Geo SCADA software license renewal dates
• Schneider Electric support contract renewal dates

Set calendar reminders 90 days before each expiration. Certificate renewals require a maintenance window, so planning ahead prevents emergency renewals under time pressure.

Windows Server Patching

Geo SCADA runs on Windows Server and requires regular patching for both security and stability. A structured patching approach includes:

• Monthly: Review and apply Windows security patches. Review Schneider Electric compatibility bulletins before applying.
• Quarterly: Apply SQL Server cumulative updates after validating against Schneider's supported versions list.
• As released: Apply Geo SCADA application updates (typically 1-2 per year) following Schneider's upgrade procedures.

Always take a verified backup before patching. Document all patches applied, including date, patch identifier, and any issues observed. For a deeper discussion of patching risks and strategies, see our article on the hidden costs of deferred ClearSCADA patching.

Backup Verification and Restore Testing

Having backups is not the same as having verified backups. A complete backup verification program includes:

• Daily: Confirm backup jobs completed successfully. Check for errors in backup logs and verify backup file sizes are consistent with expected database size.
• Monthly: Restore the most recent backup to a test environment and verify the database is accessible and data is intact. This is the only way to confirm your backups are actually usable.
• Quarterly: Perform a full disaster recovery drill — restore the database, reinstall Geo SCADA if necessary, verify client connectivity, and confirm communication to remote sites. Document the time required for each step and update recovery time estimates.

Communication Channel Health

Geo SCADA communication health goes beyond "is the site online." A thorough communication check includes:

• DNP3 statistics: Review poll success rates, response times, and timeout events per outstation. Increasing timeout rates may indicate deteriorating communication quality before a complete failure occurs.
• Modbus diagnostics: Check CRC error rates and retry counts. Elevated CRC errors on serial Modbus links often indicate wiring problems, ground loops, or failing serial-to-TCP converters.
• Cellular signal quality: If accessible, review signal strength (RSSI/RSRP) and signal quality (SINR) metrics from cellular modems at remote sites. Degrading signal quality may indicate antenna problems or carrier network changes.
• Channel redundancy: If backup communication paths are configured, verify they function correctly by testing failover periodically. A backup communication path that hasn't been tested may not work when the primary fails.

Performance Baseline Metrics

Establish and maintain baseline metrics for key performance indicators:

• Server CPU utilization during peak and off-peak periods
• SQL Server query response times for common operations (trend data retrieval, alarm summary queries)
• ViewX client login time
• Database size growth rate (GB per month)
• Communication driver scan cycle completion time

Compare current metrics against baselines monthly. Gradual degradation in any metric indicates an emerging issue that should be investigated before it causes a failure.

This checklist covers the essential maintenance items that keep a Geo SCADA platform healthy and reliable. For organizations that lack the time or expertise to execute this checklist consistently, managed Geo SCADA services from NFM Consulting include all of these tasks as standard deliverables.