shc backup mount
shc backup mount
Section titled “shc backup mount”mount a backup as a read-only FUSE tree (on the daemon host)
Synopsis
Section titled “Synopsis”Mount a backup as a read-only FUSE tree. The mount is daemon-resident: it lives on the daemon’s host and survives this CLI exiting; release it with shc backup umount <id-or-path>. Omit the mountpoint to let the daemon allocate one under its state dir (printed in the response).
shc backup mount [mountpoint] [flags]Options
Section titled “Options” --file string .bak / .bkg file to mount (not yet supported, use --id) -h, --help help for mount --id string backup ID to mount --writable accepted for Python-CLI compatibility; ignored, restic mounts are read-onlyOptions 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: $SHC_ENVIRONMENT) --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)SEE ALSO
Section titled “SEE ALSO”- shc backup - create and manage backups
shc@docs:~$