Administration
Backup and recovery
Backups are run by ArkCloud; there is no backup or restore screen for an organisation. This page states the current arrangement plainly, including its limits, so it can be weighed before patient data goes in.
Written for: Organisation administrators · Security and compliance reviewers
How the service is backed up today
| Field or control | What it means |
|---|---|
| What | A dump of the whole database, taken daily at 02:30 server time by a scheduled task. Each dump is checked by listing its contents, not by restoring it. |
| Kept for | 14 days. |
| Where | On the same disk as the live database. There is no off-site or off-host copy: the backup script can make an encrypted off-host copy, but no destination or key is configured. |
| Encrypted | No. The backup files are not encrypted, and neither is the server's data disk. |
| Standby / failover | None. The application and database run on a single server. |
| Encryption keys | The keys that protect encrypted patient fields are not included in the backups. |
| Restore | Performed by ArkCloud. A full restore was rehearsed once, on 1 October 2026, into an isolated test database; no restore of production has been performed and the rehearsal is not scheduled to repeat. There is no per-organisation or point-in-time restore. |
What that means for you
What an organisation can do
- Export the records you would need to keep working - reports, account lists, CSV exports of facilities and payers - on a schedule that suits you.
- Ask ArkCloud for the current status of off-site and encrypted backups before go-live, and record the answer in your own risk assessment. See security and compliance.