Stacks
Back up and restore a stack
LiveUse S3-backed named-volume archives to protect and recover stateful stack data.
Goal
Create and restore stack backups with correct expectations about what is and is not preserved.
Current status
Live
This area is documented as current, user-reliable behavior.
Workflow
- 1Create a stack backup from the stack detail page.
- 2Wait for each volume archive to complete.
- 3Restore only from a completed backup and monitor recovery state until deployment finishes.
What a stack backup captures
- Named-volume archives stored in S3
- The release snapshot required to redeploy the stack shape
- Per-volume status so you can see exactly which archive failed or completed
What it does not mean
- A completed backup does not mean every possible app-level consistency concern is solved for you.
- Restore is about getting the stack data and stack shape back into a usable state, not about reversing every application-side migration.
- You should still verify the application after restore instead of assuming success from the status badge alone.
Expected result
Your stack data can be archived and restored through the platform.
Common failures
- Backup storage not configured
- Agent too old for volume endpoints
- Volume restore fails before deployment resumes