Documentation

Backups

Protect your data with automated database backups and volume snapshots. Stage restores before you redeploy a service.

Database backups

Managed PostgreSQL services use pgBackRest for automated backups and point in time recovery. Managed MySQL, MongoDB, and Redis services use verified logical archives stored in the platform backup destination.

  • Automatic pgBackRest backups for PostgreSQL.
  • Verified RDB archive backups for Redis.
  • Manual and scheduled mysqldump backups for MySQL. Restores replay the dump into a fresh data directory; grants on schemas other than the service database are not restored.
  • Manual and scheduled mongodump archive backups for MongoDB.
  • PostgreSQL point in time recovery (PITR) via WAL archiving.
  • PostgreSQL, MySQL, and Redis restores stage a replacement volume on the existing service.
  • MongoDB restore and PITR are planned follow-up work.

Volume snapshots

Volumes can be snapshotted on demand to capture the full filesystem state. Snapshots are useful for migrations, staging data, and recovery workflows.

  • Create a snapshot before risky migrations or major releases.
  • Restores stage a new volume for the same service.
  • Keep snapshots organized by environment and date.

Recovery workflow

  1. Start a restore from the backup or snapshot you want to recover.
  2. nouva creates a staged volume on the current service without swapping it immediately.
  3. Apply the staged change to redeploy that service with the restored volume mounted.

Storage allowance

Backups keep their existing retention rules and do not count against the workspace's 10 GB object storage allowance. That allowance applies only to customer-created buckets.