Skip to main content
Question

error with policy backup, can not make generic storage backup

  • November 4, 2025
  • 3 comments
  • 30 views
S

Hello, I have an issue with a policy, when then runs I get this problem:

- cause:
    cause:
      cause:
        cause:
          cause:
            fields:
              - name: pvcName
                value: dashboard-ace
            file: kasten.io/k10/kio/kanister/pod.go:178
            function: kasten.io/k10/kio/kanister.PodOptions
            linenumber: 178
            message: Failed to find kanister-sidecar container with required volume mounted
          file: kasten.io/k10/kio/kanister/snapshots/snapshots.go:360
          function: kasten.io/k10/kio/kanister/snapshots.kanisterOptions
          linenumber: 360
          message: Failed to get workload options.
        fields:
          - name: pvcName
            value: dashboard-ace
          - name: namespace
            value: cp4i
        file: kasten.io/k10/kio/exec/phases/backup/snapshot_data_phase.go:885
        function: kasten.io/k10/kio/exec/phases/backup.basicVolumeSnapshot.basicVolumeSnapshot.func1.func2
        linenumber: 885
        message: Error snapshotting volume
      fields:
        - name: appName
          value: dashboard-ace-dash
        - name: appType
          value: deployment
        - name: namespace
          value: cp4i
      file: kasten.io/k10/kio/exec/phases/backup/snapshot_data_phase.go:896
      function: kasten.io/k10/kio/exec/phases/backup.basicVolumeSnapshot
      linenumber: 896
      message: Failed to snapshot volumes
    file: kasten.io/k10/kio/exec/phases/backup/snapshot_data_phase.go:406
    function: kasten.io/k10/kio/exec/phases/backup.processVolumeArtifacts
    linenumber: 406
    message: Failed snapshots for workload
 the way we installed kasten was:
helm install k10 kasten/k10 \
  --namespace kasten-io \
  --version 8.0.9 \
  --set scc.create=true \
  --set route.enabled=true \
  --set route.path="/k10" \
  --set auth.tokenAuth.enabled=true \
  --set genericStorageBackup.token="adsfa…." \

 

we tried before adding the flag:   --set injectGenericVolumeBackupSidecar.enabled=true\
But the project we need to backup doesn’t have the correct permission to create and execute the kanister sidecard containers. So  we don’t know the way to take backup of the kind of PVC
they use file Storage CSI Driver of IBM and doesn’t have snapshot capability so we try to use GSB but we have this issue with the sidecar.
BTW, the app we need to backup we can not change the permissions.

3 comments

pablo.aguilar
Forum|alt.badge.img

Hola Sebastian! como estas?.. Primero gracias por compartir tu consulta, segundo.. en VUG Argentia podes compartir en castellano.

 

Con respecto al error, te acerco unos pasos para que pruebes, con los links de consultas.

  1. Ensure the helm flag stays on (you already tried it):
    --set injectGenericVolumeBackupSidecar.enabled=true. docs.kasten.io

  2. Give K10 permission to mutate workloads in that namespace so it can inject the sidecar:

 

kubectl create rolebinding k10-kanister-rb \ -n cp4i \ --clusterrole=kanister-executor \ --serviceaccount=kasten-io:k10-k10

(Adjust SA name/namespace if yours differs.) docs.kasten.io

  1. Force GSB on that app (if you’re not using a preset that already does it):

 

kubectl annotate deploy/dashboard-ace-dash \ -n cp4i \ k10.kasten.io/forcegenericbackup="true" --overwrite

(Useful when GitOps or other controllers don’t set it.) community.veeam.com

  1. On OpenShift, if SCC blocks the injected container because of user IDs/FSGroup, make sure the sidecar inherits the primary container’s securityContext (fixed behavior in recent K10), or align SCC to permit the same UID/FSGroup your app already uses. docs.kasten.io

After these, re-run the policy. If you hit “/tmp not writable” inside the sidecar, add an emptyDir /tmp mount to the sidecar (known GSB issue/workaround). Veeam Software

 

Cualquier duda seguimos por aca.

 

Saludos

Playad1t0
waqasali
Forum|alt.badge.img+4
  • waqasali
  • On the path to Greatness
  • November 5, 2025

Check that the appliance has proper connectivity and credentials for the storage. If the issue persists, review logs for the exact error and consider recreating the policy. If still issue not resolved, try to open a case with veeam support and provide them logs for further investigation.

Waqas Ali
S

Hola pablo tres preguntas :

  1. generic storage lo estamos usando para realizar backups de pVC con file storage, por defecto, los sidecars solo se crean en los deployment que tengan estos pvcs? o en cualquier deployment a pesar que los otros si terngan PVC que soporten snapshots por CSI ?
  1. Estos sidecars solo se crean en los namespaces que indique al momento de crear la policy ?
  2. Para usar estas banderas que me indicas, tengo que reinstalar kasten o solo con helm upgrade ?

Esto te lo pregunto porque también realizamos pruebas instalando kasten con la bandera de los sidecars pero nos presentó los problemas de accesos en namespaces propios de openshift y no dejaba realizar actualizaciones correctamente.
Creería que en el momento de la instalación o el upgrade le puedo indicar a que elementos puede crear sidecars

 

Terms & ConditionsAccessibility statement