Hi ​@pascalTower t’s not possible to eliminate the retries, but I recommend reducing the blueprint backup timeout. This way, the three retries won’t consume as much time.


please review the below link for more details
https://docs.kasten.io/latest/install/helm.html

BR,
Ahmed Hagag

For the blueprint actions timeouts, these keys are kept in the
ConfigMap: k10-config -namespace kasten-io

As values: 

  K10TimeoutBlueprintBackup: "45"  (min)

  K10TimeoutBlueprintDelete: "45"  (min)

  K10TimeoutBlueprintHooks: "20"  (min)

  K10TimeoutBlueprintRestore: "600"  (min)


You can lower these values to, say, not wait 45 minutes for a backup attempt to fail. Just dont make them too low or you can cause failures if resources do not come ready in short timeframes. 

Incidentally, you can also raise these values if you have a large volume or slow storage that takes a while to snapshot clone for export.