Core model
- Restore is a target operation, not just an import step
- Service, healthcheck, proxy, and database belong to the same path
- Verification is part of recovery
- Deploy is the user-facing restore command
Restore model
MoveStack’s verified restore model
How MoveStack treats restore as a complete target workflow: from snapshot into target, through service readiness, to database verification.
For MoveStack, restore does not end when data has been copied back. Recovery is only successful when the target is working again and the restored state is verified.
How MoveStack handles restore
MoveStack restores a snapshot or archive into a target environment, brings the app back up, and then verifies service, healthcheck, proxy, and database state together. Recovery stays one operational workflow.
Why that matters
A database import alone does not prove the app is usable again. If runtime, environment, proxy, or healthchecks fail afterward, the restore was not operationally complete.
Core facts
Verified restore belongs to the licensed path
Deploy and clone build on the same target model
Database fingerprinting is part of restore verification
Watch and monitor expose recovery progress and final state
FAQ
Is deploy the same thing as restore?
Deploy is the user-facing restore command. Restore dry-run and restore run are the lower-level commands.
What does verified restore mean?
It means the recovery flow also checks service, healthcheck, proxy, and database state after the restore.