Backups
Use backup policies and backup runs to protect relational database clusters (MySQL and PostgreSQL), then restore a run into a new cluster. Document databases and caches have parallel backup flows under their own services.
Components
| Component | Description |
|---|---|
| Backup policy | Schedule (cron), retention, and backup source (primary or replica) |
| Manual backup | On-demand backup run for a cluster |
| Backup run | A completed or in-progress backup stored in Object Storage |
| Restore | Create a new cluster from a ready backup run |
In the console
Choose Databases, then:
- Backups Policies — create and manage policies
- Backup Runs — account-wide overview of runs
- Open a cluster — attach policies, set the backup bucket, and open cluster backup runs
Typical order
- Create a backup policy.
- On the cluster, attach the policy and confirm the backup bucket.
- Wait for scheduled runs, or start a manual backup.
- (Optional) Restore a ready run into a new cluster.
Note
When you create a cluster, myStack provisions Object Storage for backup artifacts and a dedicated data key that encrypts those backups. A master key is not created by default. See Object Storage for bucket details.