Goal
Create and restore stack backups with correct expectations about what is and is not preserved.Prerequisites
- A stateful stack with named volumes
- S3 backup storage configured
- A healthy node agent
Workflow
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
Related guides
Reassign and migration expectations
Understand what stack reassignment and migration mean today, especially for stateful stacks.
Recovery states, logs, and troubleshooting
Read the operation state on a resource — its status, current step, attempt count, retryable flag, and last error — together with logs, instead of treating a single “error” badge as the whole story.