stackkit backup

stackkit backup [flags]

# Configure the local Kopia repository after stackkit apply
stackkit backup configure

# Take a snapshot now
stackkit backup run

# Check repository readiness and the latest snapshot and restore receipts
stackkit backup status

# Restore a snapshot into isolated staging
stackkit backup restore sha256:<snapshot-anchor-id> --owner-approve

stackkit backup configure [flags]

# Configure the repository once the Basement core is applied
stackkit backup configure

# Configure it and print the command result as JSON
stackkit backup configure --json

stackkit backup emergency-export [flags]

# Export the generated backup contract, encrypted to your age public key, into a new directory
stackkit backup emergency-export --recipient <age-public-key> --target /mnt/usb/stackkit-export

# Export explicit paths when no generated contract exists
stackkit backup emergency-export --recipient <age-public-key> --target /mnt/usb/stackkit-export --source config=/opt/stacks --source user-content=/opt/data

stackkit backup emergency-restore [flags]

# Decrypt and verify an export into a new staging directory with your age identity file
stackkit backup emergency-restore --archive <export-dir>/<archive>.tar.gz.age --identity-file ~/.config/age/key.txt --target ./restore-staging

stackkit backup init [flags]

stackkit backup restore <snapshot-anchor-id> [flags]

# Restore a snapshot into isolated staging; the live volumes are not touched
stackkit backup restore sha256:<snapshot-anchor-id> --owner-approve

# Print the result as JSON: data.id is the restore result ID for restore activate, data.operationId is the restore operation ID for restore abandon
stackkit backup restore sha256:<snapshot-anchor-id> --owner-approve --json

stackkit backup restore abandon <restore-operation-id> [flags]

# Discard a staged restore you do not want to activate
stackkit backup restore abandon <restore-operation-id> --owner-approve

stackkit backup restore activate <restore-result-id> [flags]

# Replace the live volumes with a verified staged restore
stackkit backup restore activate sha256:<restore-result-id> --owner-approve

# Name the activation operation so an interrupted run can be recovered by that ID
stackkit backup restore activate sha256:<restore-result-id> --owner-approve --operation-id restore-activate-2026-09-18

stackkit backup restore recover <activation-operation-id> [flags]

# Recover an interrupted activation by its operation ID
stackkit backup restore recover restore-activate-2026-09-18 --rollback --owner-approve

stackkit backup run [flags]

# Take a snapshot now; data.id in the JSON result is the snapshot anchor ID for backup restore
stackkit backup run --json

# Use your own operation ID so a retry cannot create a second snapshot
stackkit backup run --operation-id manual-2026-09-18

stackkit backup schedule [flags]

stackkit backup schedule disable [flags]

# Stop scheduled snapshots and revoke their authorization
stackkit backup schedule disable --owner-approve

stackkit backup schedule enable [flags]

# Approve the backup cadence from the applied plan and start its timer
stackkit backup schedule enable --owner-approve

stackkit backup schedule status [flags]

# Show the timer, its authorization, and the last scheduled snapshot
stackkit backup schedule status

# The same status as JSON
stackkit backup schedule status --json

stackkit backup status [flags]

# Show repository readiness, coverage, and the latest snapshot and restore receipts
stackkit backup status

# The same status as JSON
stackkit backup status --json

stackkit backup target [flags]

stackkit backup target import [flags]

# Import the S3 target from a private JSON file with the fields listed above
stackkit backup target import --owner-approve < s3-target.json

stackkit backup target recipient [flags]

stackkit backup target recipient --challenge "$CHALLENGE" --owner-approve

stackkit backup target status [flags]

# Confirm the imported target custody is intact
stackkit backup target status