Skip to main content
SynaptaGrid Platform
← All capabilities
Available now

Platform capability · Backup & Disaster Recovery

Restore customer data from encrypted backups

Encrypted backups and point-in-time restore

Because each customer’s data is kept apart, a backup and a restore have a clear scope. The platform’s provisioning creates encrypted database storage with automated backups, a retention period and point-in-time recovery on every deployment size. A dedicated database gives an enterprise customer a restore that covers only that customer. Eligible Aurora deployment sizes can add a secondary copy in another region.

Built in

What you get

  • Customers with a dedicated database get a restore that covers only their data. Customers on shared databases are kept apart inside a shared backup
  • Automated database backups with a retention period and point-in-time recovery, set up by the platform’s provisioning
  • Customers on plans that include backups create and restore them from the portal, for each app instance. Backups are not offered as downloads, and trial plans do not include them
  • File storage versioning and replication to another region can be turned on
  • Backups are encrypted with managed keys when the deploying operator configures it
  • Restore an app’s database from a backup into a new database, then switch over
  • Move a customer to a larger database size, with a rollback window that is shown before it closes
Under the hood

How it works

What is available today and what is planned

The platform’s provisioning sets up backup retention, point-in-time recovery and encryption as part of the infrastructure definition. A dedicated database for one customer, and so a restore that covers only that customer, is an enterprise upgrade. Cross-region replication still has to be turned on for each production tier. Recovery is not proven until the documented restore drills have been run.

Recovery targets are design goals

The recovery targets are design goals. Critical services such as sign-in, permissions and the platform’s core services should be back within one hour and lose at most five minutes of data. Other services should be back within four hours and lose at most one hour. Standby read replicas are available on Large and Extra Large deployments.

Further additions

Additions that extend the capability described above.

  • Recovery targets (RTO and RPO) for each class of service
  • Cross-region backup replication turned on for each production tier
  • Documented runbooks for each recovery scenario
  • Quarterly restore drills
Pairs well with

Related capabilities

Multi-tenancy

Checks on every request, a separate database, or dedicated infrastructure

Observability

OpenTelemetry, traces, logs and dashboards

Audit

An audit trail that can only be added to, where tampering shows

Want a deeper walkthrough of Backup & Disaster Recovery?

A solution architect will demo the live service against your domain model.

Get a deployment assessment