Rollbacks
Roll back databases and services to a previous state.
Rollbacks let you quickly revert a database or service to a known-good state after a failed deployment or data issue.
Database rollbacks
Database rollbacks use either backup restore or point-in-time recovery under the hood.
Restore to a backup
- Navigate to your database's Backups tab
- Select a backup from the list
- Click Restore and confirm
Restore to a specific time
- Navigate to your database's Backups tab
- Click Point-in-Time Recovery
- Select the target time and confirm
Service rollbacks
For services, rollback means restoring to a previous deployment image or volume snapshot.
Redeploy a previous image
- Navigate to your service's Deployments tab
- Find the previous deployment you want to roll back to
- Click Redeploy to launch that image version again
This creates a new deployment with the old image. Environment variables and configuration use their current values.
Restore a volume snapshot
If your service uses persistent storage:
- Navigate to the Backups tab
- Select a volume snapshot
- Click Restore and confirm
The service will restart with the restored volume.
Best practices
- Always take a snapshot or backup before risky operations
- Test rollback procedures periodically
- Keep notes on which deployment versions are known-good
- Use descriptive commit messages so you can identify good versions quickly