13. Backup, monitoring and recovery

The value of a backup is shown not the night it runs, but the morning you really need it.

Why this station counts

X-ERP requires consistent backup of XLD and all company databases as well as appropriate configuration, key and certificate evidence. Monitoring supplements this with availability, errors, runtime, storage and expiration dates.

The resilient process

1. Define RPO, RTO, retention, encryption and responsible parties.
2. Back up XLD and company databases consistently and separately from the primary system.
3. Securely capture recovery-related configuration, certificates, and keys.
4. Monitor services, HTTP status, SQL jobs, backup age, storage, logs and certificate expiration.
5. Periodically restore in an isolated environment and run an X-ERP functional test.

Functional test - only then continue

• Last successful backup and its age are visible.
• Restore reaches the agreed time and data status.
• XLD and company mapping work after restore.
• Alarms reach a responsible person and are practiced.

If the result is not correct

• Backup and original are at the same error location.
• Restore was never checked against the X-ERP login.
• Alarms exist, but no one has preparedness or an escalation route.

This is what you take with you

You can not only hope, but prove that X-ERP will return in a controlled manner after a failure.

Further information / source

Related topics

1. For system administrators – setting up servers and creating company databases › 01. System architecture and technical structure
2. For system administrators – setting up servers and creating company databases › 14. Updates and operational documentation

Frequently asked questions