Skip to main content
The released Basement Kit includes a local, owner-controlled Kopia backup lifecycle. Run it only from the applied StackKits workspace whose data you intend to protect.

​
Configure and check the repository

The repository, source set, exclusions, and local custody are derived from the resolved plan. Do not point the command at an arbitrary volume or bypass owner custody.

​
Create an idempotent snapshot

Store the returned content-addressed snapshot anchor with your verification evidence. Reusing the same operation ID returns the existing operation instead of creating an accidental duplicate.

​
Restore into isolated staging

This verifies and extracts the snapshot into CUE-owned staging. It does not replace live data. Review the returned restore-result ID before continuing.

​
Activate the verified restore

Activation creates the required safety snapshot, switches the exact plan-owned volume set, restarts the runtime, and verifies the owner binding and services. If activation is interrupted, recover the exact operation explicitly:
A successful backup is not recovery proof. Practice the staged restore with non-critical data before relying on the stack for irreplaceable files.