Checkpoints and Rollback Preview
Checkpoint service definiert records, retention behavior, REST/MCP operations und rollback state machine für apps.
Noch keine echte Recovery: active snapshot adapter fabricates VM und database snapshot identifiers. Stop/start/health stages simulated, no disk or database state captured or restored. Checkpoint created today ist kein backup und must not used as recovery control.
Was getestet werden kann
Preview surface lets integration developers exercise:
- manual checkpoint creation und listing;
- pin, unpin, delete und retention metadata;
- ownership checks;
- rollback state transitions; und
- creation of pre-rollback safety record.
Following MCP tools expose that control plane:
| Tool | Preview behavior |
|---|---|
create_checkpoint | Creates record with stub snapshot identifiers |
list_checkpoints | Lists owned records und reported usage |
pin_checkpoint | Exempts record from retention pruning |
delete_checkpoint | Deletes unpinned record |
rollback_app | Exercises simulated rollback sequence |
Describe successful response from these tools nicht als recovered app.
Production recovery today
For immutable app deployment recover from source und separately managed data:
- identify known-good Git revision;
- confirm database or object-store backup exists und can be restored;
- queue new immutable deployment for that revision;
- restore data through service documented recovery procedure; und
- verify application health und user-visible behavior before switching traffic.
Keep backup retention, restore testing und recovery objectives outside checkpoint preview until real adapters shipped und passed restore drill.
What remains
- real VM und database snapshot primitives;
- rollback integration with immutable variant deployment pipeline;
- failure-atomic restore behavior;
- deploy hooks creating verified checkpoints;
- capacity und retention enforcement against real storage; und
- backup/restore drills with captured evidence.