Skip to content
SHC Docs

shc backup clear-restore-seal

lift the restore seal that is refusing a first-boot seed job on a deployment

Lift the restore seal a restore left on a deployment.

A restore marks the deployment it replayed, and while that mark stands SHC refuses any hook job it recognises as a first-boot seed ceremony (a job that drops tables or re-runs a product’s install command) on that deployment and on every consumer bound to it. That refusal exists because such a job, run against restored data, deletes it while every surface reports success.

You should not normally need this command: a standalone restore lifts its own seal once it has verified the data survived the bring-up, and a recover releases every seal it armed when the whole plan is done. Use it when a recover died mid-flight, or when the seal is unreadable, or when you have satisfied yourself by hand that the deployment’s data is what it should be.

Acts on the deployment directory on this node; run it where the deployment lives.

shc backup clear-restore-seal [flags]
-h, --help help for clear-restore-seal
-s, --stack string stack name (overrides ctx)
-y, --yes skip confirmation prompt
--config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win
-d, --debug enable debug mode (default: $SHC_DEBUG)
-e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default")
--exclude string comma-separated dotted paths to drop
--fields string comma-separated columns/keys to show (and their order)
--filter string comma-separated dotted paths to keep (drops everything else)
-o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT)
-t, --tenant string tenant name (default: $SHC_TENANT)
-v, --verbose verbose output (default: $SHC_VERBOSE)