Skip to content
SHC Docs

shc volume snapshot

take a cloud point-in-time snapshot of a block volume

Take a provider-side point-in-time snapshot of a block volume and print its snapshot handle.

Snapshots are pre-move safety points and fast restore sources. They complement backups and do not replace them: a snapshot lives in the same cloud account as the volume it copies.

The volume may stay attached: a cloud snapshot of an attached volume is crash-consistent. Backends whose cloud has no volume-snapshot primitive (Hetzner among them) refuse with a message naming the upstream limitation.

shc volume snapshot <volume-id|name> [flags]
-h, --help help for snapshot
--name string name for the snapshot (default: a derived shc-snap-… name)
--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)
-s, --stack string stack name (default: $SHC_STACK)
-t, --tenant string tenant name (default: $SHC_TENANT)
-v, --verbose verbose output (default: $SHC_VERBOSE)
  • shc volume - manage and inspect cluster block volumes