14. Updates and operational documentation

A system does not remain stable by leaving it unchanged. It remains stable by preparing, observing and repeating every necessary change.

Why this station counts

The components have different life cycles, but they interconnect. An update plan must therefore address the version matrix, database changes, maintenance windows, user communication and fallback together.

The resilient process

1. Maintain an inventory of X-ERP, .NET, SQL, Windows, Certificate and third-party component versions.
2. Read release notes and check dependencies in a representative test copy.
3. Create current backups and test the fallback path.
4. Define maintenance windows, responsible parties, success criteria and communication.
5. Update in a documented order and monitor logs, services and core processes.
6. Conclude with acceptance, version status and lessons learned.

Functional test - only then continue

• Version matrix is current.
• Test covers login, receipt, attachment, interface and critical evaluation.
• Termination criteria and relapse are practically possible.
• Operating file contains changes, results and those responsible.

If the result is not correct

• Uncoordinated automatic updates change operational times.
• Testing just the homepage misses technical regressions.
• Undocumented manual work cannot be reproduced in the next system.

This is what you take with you

Updates become controlled operations rather than bets on a quiet Monday morning.

Further information / source

Related topics

1. For system administrators – setting up servers and creating company databases › 13. Backup, monitoring and recovery
2. For system administrators – setting up servers and creating company databases › 01. System architecture and technical structure

Frequently asked questions