stackkit backup configure, stackkit backup emergency-export, stackkit backup emergency-restore, stackkit backup init, stackkit backup restore, stackkit backup run, stackkit backup schedule, stackkit backup status, stackkit backup target
stackkit backup configure
Configure the CUE-governed local Kopia repository. Configure the local Kopia repository from the exact generated StackSpec v2 backup policy. The repository path and kopia-agent service are CUE-owned and cannot be overridden at the command line.
Examples
stackkit backup emergency-export
Export selected local data as an encrypted portable recovery archive. Create a portable age-encrypted tar/gzip archive with per-file checksums and a restore runbook. Provide an age recipient public key and a new target directory outside the sources. Omit--source to export the generated v2 backup contract (CUE emergencyExport classes plus the generate/apply source-policy volumes). Explicit CLASS=PATH sources remain the standalone path when no generated contract is present. File copying does not prove application consistency; stop writers or export database-native dumps first. Recovery stages data without the original host, Kopia, or a Kombify account.
Examples
stackkit backup emergency-restore
Decrypt and verify a portable export into a new staging directory.
Examples
stackkit backup init
Print first-run setup instructions. Print the first-run setup steps for the backup addon. This command is read-only. It describes the native lifecycle that renders and applies the CUE-owned local kopia-agent before repository configuration.stackkit backup restore
Verify and restore a signed snapshot into isolated staging. Restore one content-addressed, owner-signed snapshot anchor into the CUE-owned isolated staging volume. The raw Kopia snapshot ID and staging path are not caller-controlled.--owner-approve records explicit local Owner authorization; this command never requires a Kombify account or Cloud service.
Examples
stackkit backup restore abandon, stackkit backup restore activate, stackkit backup restore recover
stackkit backup restore abandon
Abandon one pending or staged restore operation.
Examples
stackkit backup restore activate
Activate one verified staged restore into the live Basement volumes.
Examples
stackkit backup restore recover
Recover an interrupted restore or finish its committed result. Recover the exact owner-approved restore activation. Before commit, recovery restores the prior live volumes. After commit, it preserves the activated data and resumes result cleanup and application finalization. Repeating recovery for a completed operation returns its original signed result.--rollback is required.
Examples
stackkit backup run
Force a snapshot now (out of band).
Examples
stackkit backup schedule
Control the Owner-approved local backup timer.
Subcommands:
stackkit backup schedule disable, stackkit backup schedule enable, stackkit backup schedule status
stackkit backup schedule disable
Revoke scheduled backup execution and stop its timer.
Inherited from
stackkit backup schedule:
Examples
stackkit backup schedule enable
Approve and enable the exact CUE backup cadence.
Inherited from
stackkit backup schedule:
Examples
stackkit backup schedule status
Show timer, authorization and last scheduled snapshot separately.stackkit backup schedule:
Examples
stackkit backup status
Show local Kopia repository status.
Examples
stackkit backup target
Bind an owner-supplied S3 target to the generated backup policy.stackkit backup target import, stackkit backup target status
stackkit backup target import
Import encrypted S3 custody from JSON on stdin. Import JSON fields endpoint, bucket, prefix, region, accessKeyId, secretAccessKey and passphrase from stdin. The passphrase is a string for an existing Kopia repository. Only opaque target references are printed. This imports custody; it does not create a bucket or verify offsite readiness.
Examples