Kopiur
Kopiur backs up PVCs with Kopia. Each Snapshot holds one PVC. bret restores each Snapshot
into a scratch PVC through a Kopiur Restore and runs the check against all of them. Kopiur
support in bret is alpha.
How it works
Section titled “How it works”- For each source, bret reads the
Snapshotnamed bybackupRefand checks that it backs up thesourcePVCof the source. Otherwise theRestorefails withSourceMismatch. - It creates a Kopiur
Restorewithsource.snapshotRef,target.populator: {}andpolicy.onMissingSnapshot: Fail. When a mover UID is known, it setsmover.securityContextandmover.podSecurityContext.fsGroup. - It creates the scratch PVC with a
dataSourceRefto the KopiurRestore. Kopiur fills it as a volume populator. - When every Kopiur
Restorehasstatus.phase: Completedand conditionReady=True, bret runs the check pod with all scratch PVCs mounted. - On cleanup the operator deletes the Kopiur
Restoreobjects and the scratch PVCs.
Without size, bret sizes the scratch PVC from the source with autoExpand: by default 10
percent headroom and at least 1Gi. Details:
Scratch volume size.
Next steps
Section titled “Next steps”- Add bret to an existing Kopiur setup: the checklist.
- Walkthrough: a WordPress + MariaDB example from install to
RestoreTest. - Limitations: what bret cannot do with Kopiur, and fixes.
Install Kopiur
Section titled “Install Kopiur”Skip this if Kopiur already runs. Install Kopiur with its Helm chart into kopiur-system, as the
Kopiur docs describe. Tested with Kopiur 0.11.0 on kind with Kubernetes 1.37. Upstream issue
kopiur#233 affects restores and is still open.
The provider is on by default in the bret chart (providers.kopiur.enabled: true).
