SCHOOL MANAGEMENT · CONTINUITY
School ERP Backup and Data Recovery: Questions Schools Should Ask Their Vendor
Questions that help school leaders understand backup scope, recovery processes, responsibilities, evidence and continuity during service disruption.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
Ask what data is backed up, how often, how long copies are retained, how restoration is tested, who may request recovery and what recovery timing the provider commits to. Also define the school’s own continuity steps during an outage. Do not treat a general backup claim as proof of a particular restore point, recovery time or guaranteed outcome.
01 / BACKUP SCOPE
Ask what information and service components are included.
Clarify whether backups cover operational records, documents, configuration, user relationships and other service data. Ask what is excluded and whether any school-maintained information sits outside the provider’s backup boundary.
Distinguish a database backup from a complete service recovery plan. The school needs to understand which parts of its work can be restored and which require separate preparation.
02 / FREQUENCY & RETENTION
Understand how much recent work could be affected by a recovery point.
Ask how frequently backups are created, how copies are protected and how long they are retained. Relate the answer to the school’s busiest operating periods and the amount of re-entry it could tolerate.
Do not infer a specific recovery point from ‘regular backups’. Request the provider’s current documented policy and clarify whether different data categories have different schedules.
03 / RESTORE TESTING
Ask how restoration is tested and what evidence the provider can share.
A backup is useful only if it can be restored within a practical process. Ask how often tests occur, whether they cover representative service components and how test findings are addressed.
Confirm who approves a restore, how the school is notified and whether restoration can affect current records. Avoid relying on a past success anecdote as a guarantee for a future incident.
04 / RECOVERY EXPECTATIONS
Clarify service recovery targets and what they do—and do not—promise.
Ask the provider to explain any recovery time or recovery point objectives, their scope, assumptions and exceptions. Understand whether the figures are contractual commitments, planning targets or informational descriptions.
Record how the school will receive updates and who decides when the service is ready for normal use. Request support documentation instead of translating technical terminology into an unverified guarantee.
05 / SCHOOL CONTINUITY
Prepare a manual fallback for essential school work during an outage.
Identify which tasks cannot wait, who may authorise a temporary record and how later updates will be reconciled. Keep the fallback limited and secure so it does not create an uncontrolled parallel database.
Define communication channels and contact responsibilities. The school should know how to continue critical work while respecting student privacy and preserving a clear record of temporary decisions.
06 / CONTRACT & REVIEW
Keep recovery answers with the agreement and revisit them over time.
Document provider commitments, exclusions, escalation contacts and any separately scoped recovery service. Ask how subscription changes or termination affect access to backups and exports.
Review the plan periodically and after major changes to the school’s operating model. Backup readiness is shared responsibility between provider commitments and institution-owned continuity practices.
A FIELD GUIDE FOR YOUR TEAM
A vendor backup and recovery review
Use these questions to translate technical statements into school-specific continuity expectations.
| Lens | Question to ask | What to record |
|---|---|---|
| BACKUP SCOPE | Ask what information and service components are included. | A written backup scope and explicit exclusions. |
| FREQUENCY & RETENTION | Understand how much recent work could be affected by a recovery point. | Documented backup intervals and retention terms. |
| RESTORE TESTING | Ask how restoration is tested and what evidence the provider can share. | A described test process and evidence appropriate to the service. |
| RECOVERY EXPECTATIONS | Clarify service recovery targets and what they do—and do not—promise. | A plain-language interpretation of documented recovery expectations. |
| SCHOOL CONTINUITY | Prepare a manual fallback for essential school work during an outage. | A tested, minimal continuity procedure with reconciliation ownership. |
| CONTRACT & REVIEW | Keep recovery answers with the agreement and revisit them over time. | A dated recovery review and accessible provider contact record. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
Current School ERP hosting, backup and disaster-recovery commitments should be confirmed through approved provider documentation. This guide does not assert a specific backup frequency, retention period, recovery objective or certification.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.