DATA
Backups
Automated and manual backups for your databases and infrastructure — with retention you control, clear restore points and a choice of where backups are kept.
Restore points
acme / my-app / productionRESOURCETYPETRIGGERSTORED IN
main-db DatabaseAutomatedCanada Central
main-db DatabaseManualCanada Central
web-server ServerAutomatedCanada East
Backup policy · main-db schedule: daily · retention: [retention period] · region: canada-central
WHAT IT DOES
A safety net for your data and servers.
Turn on automated backups for databases and infrastructure, take manual backups before risky changes, and restore from any available restore point — from the dashboard, the API or the CLI.
Backups follow the resource's environment, so restores land in the right place.Automated schedules, plus manual backups on demand.Retention you set per resource. Options: [retention options].Choose where backups are stored, including Canada.
KEY CAPABILITIES
Everything you need to recover quickly.
Automated backups Backups run on a schedule without any scripts to maintain.
Manual backups Take a labelled backup before a migration or release.
Retention Decide how long backups are kept: [retention options].
Restore points Browse available backups and restore the one you need.
Database backups Built in for Stack53 managed databases.
Infrastructure backups Back up servers and volumes: [confirm supported resources].
Restore to a new resource Test a restore without touching the running resource.
Geographic availability Pick the storage region. Cross-region copies: [confirm availability].
Backups API Create, list and restore backups from code or the CLI.
HOW IT WORKS
From policy to restore in four steps.
- 01 Pick a resource A database or server in any environment.
- 02 Set a backup policy Schedule, retention and the region to store backups in.
- 03 Backups run Automatically, plus manual backups whenever you need one.
- 04 Restore when needed Choose a restore point and restore in place or to a new resource.
COMMON USE CASES
When teams reach for backups.
Safe migrations and releases Take a manual backup before a schema change, and roll back if something goes wrong.
Recovering from mistakes Restore deleted or overwritten data from an earlier restore point.
Data residency requirements Keep backups in Canadian regions and set retention to match your policies.
DEVELOPER INTEGRATION
Built for code.
Set backup policies, take manual backups, list restore points and start restores from the REST API, the SDKs or the CLI — the same way you manage every other Stack53 resource.
// Take a manual backup before a release
const backup = await stack53.backups.create({
resource: 'main-db',
label: 'before-release',
})
// Restore it to a new database
await stack53.backups.restore(backup.id, { target: 'new' })
SECURITY Protected like the original. Backups are private to your workspace and project.Encrypted in transit. Encryption at rest: [confirm details].Workspace roles control who can restore or delete backups.Backups and restores recorded in audit logs. Security at Stack53 →
AVAILABILITY Where it runs.
REGIONOPERATED BYSTATUS
Canada Central[Partner / Stack53][Status]
Canada East[Partner / Stack53][Status]
Protect your data today.
Start building on Stack53, or talk to us about backup, retention and data residency requirements.