Kopiur limitations
Limits
Section titled “Limits”- Alpha. Kopiur and its bret provider are young. Upstream issue
kopiur#233affects restores and is still open. - No point in time across PVCs. Each
Snapshotholds one PVC. The restored PVCs of one run can be minutes apart. See Point in time across PVCs. - Credentials Secret next to the Restore. Kopiur reads the repository credentials only in the
namespace of its
Restore. - Populator needed. The scratch PVC is filled through a
dataSourceRef. The CSI driver and the cluster must support volume populators. - One mover UID per volume. All restored files belong to that UID.
Troubleshooting
Section titled “Troubleshooting”Kopiur restore: MissingCredentialsSecret
Section titled “Kopiur restore: MissingCredentialsSecret”- Cause: the restore runs in a namespace without the repository credentials Secret.
- Fix: keep the Secret in the namespace of the
Restore. See The Kopiur-native restore.
Kopiur snapshot: PermissionDenied, cannot create iterator: unable to read directory
Section titled “Kopiur snapshot: PermissionDenied, cannot create iterator: unable to read directory”- Symptom:
kopia snapshot create ... permission deniedon a database directory. - Cause: the snapshot mover runs as UID 65532 by default. The data directory is owned by the database UID with mode 0700.
- Fix: set
spec.mover.securityContext.runAsUseron theSnapshotPolicyto the database UID (999 for MariaDB and Postgres 17).
Kopiur snapshot stays Pending, WaitingForStagedPvcBind
Section titled “Kopiur snapshot stays Pending, WaitingForStagedPvcBind”- Symptom: the condition says the staged PVC is waiting to bind.
kubectl get pvcshows the staged PVCBounda few seconds later. - Cause: a reconcile lag. The controller retries on its own.
- Fix: wait. If it stays Pending past the staging deadline in the condition message, read the
controller logs in
kopiur-system.
RestoreTest stays at BackupNotFound
Section titled “RestoreTest stays at BackupNotFound”- Cause: no
SucceededSnapshotmatches thebackupSelectorof the named source. - Fix: check the labels with
kubectl get snapshot --show-labels, and the phase. Reason:BackupNotFound.
Restore fails with SourceMismatch
Section titled “Restore fails with SourceMismatch”- Cause: the
Snapshotbacks up another PVC than thesourcePVCof the source. - Fix: select the
Snapshotsof that PVC, for example by its policy label. Reason:SourceMismatch.
