Skip to main content
Restore is intentionally destructive and requires --force:
The CLI validates the archive structure and manifest, rejects unsafe or duplicate entries, requires the core configuration and durable-state files, and verifies that the backup’s deployment identity matches the existing deployment when one is present. The restore flow stops the runtime, restores deployment configuration and durable application state, and then starts the full runtime. A backup from another deployment ID is refused rather than silently re-hosted.