SparkOS · 2.0

Backup and Recovery Policy

Scope and approved objectives

Backups cover the database, attachments, configuration and securely managed keys needed for restoration. The Service Schedule specifies frequency, retention, recovery-point objectives and recovery-time objectives for each component. Values are tested before real-data activation; unverified levels must not be advertised. A database backup alone is insufficient where separately stored attachments are not included.

Segregation and encryption

Backups are encrypted and administered separately from production, with a copy protected from modification or deletion during its protection period. Backup locations and supplier access are approved in the processing register beforehand. Key administration is restricted, and reads, restores and deletions are logged.

Monitoring and testing

The Company reviews backup-job results daily and opens an incident on failure or breach of the agreed recovery point. Isolated restoration is tested quarterly and after material changes, covering attachments, relationships, permissions and report samples. Duration, results, deficiencies and remediation are recorded. The overall disaster-recovery plan is tested annually.

Performing restoration

The impact on newer records is explained and the Clinic’s authorised approval obtained before replacement, except necessary emergency action to prevent greater harm with notice and review. The affected state is preserved for investigation where lawful and feasible. Deletion and restriction instructions are reapplied before restored historical data becomes available.

Backup and archival limits

Backups are a recovery mechanism, not a medical archive replacing retention duties or exit arrangements. Agreed objectives do not guarantee zero loss. The Company discloses missed objectives, available recovery points and impact. Copies expire under the retention policy and are not used for independent purposes.