shc backup clear-unusable
shc backup clear-unusable
Section titled “shc backup clear-unusable”clear the unusable stamp a failed recover left on a deployment
Synopsis
Section titled “Synopsis”Clear the unusable stamp a failed recover left on a deployment.
A recover that installed a deployment and then failed to restore its data leaves the stack up and empty: healthy by every derived measure, because the app booted cleanly against a fresh datastore. The stamp is what keeps that deployment from passing for a good one, and what makes the backup scheduler refuse to mint an empty archive that would age the real one out.
Restoring the deployment clears the stamp on its own, so you do not need this command for the ordinary case. Use it only when you have repaired the deployment by hand and have satisfied yourself that its data is what it should be.
Acts on the deployment directory on this node; run it where the deployment lives.
shc backup clear-unusable [flags]Options
Section titled “Options” -h, --help help for clear-unusable -s, --stack string stack name (overrides ctx) -y, --yes skip confirmation promptOptions inherited from parent commands
Section titled “Options inherited from parent commands” --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)SEE ALSO
Section titled “SEE ALSO”- shc backup - create and manage backups