Added a Kubernetes Cluster. The pods are discovered fine however during the backup I see the following on vsbkp.log and job goes into waiting state.
Error mounting snap volumes. Possible reason includes there is no FC or iscsi connectivity found with esx server. Please check whether nIscsiEnable registry key is set if you are using Iscsi method for mounting.
- Kubernetes backup failing due to Node does not have enough resources to get temporary pods created - Once customer reduced the load for the specific worker node the job was able to run and complete without issues
- CMR has been created: 325875 - Optimization logic to be o created from Commvalt side during the provisional resources needed
@Mike Struening Thanks for tagging me. The error comes from us failing to mount / create a snapshot of the PVC. Like @rohit mentioned, the error reporting has been enhanced in recent FRs to have more K8s specific language.
@TNO do you have additional context from vsbkp.log? We’ll need a few more lines of context to see what the exact failure was. Alternatively if you have already have a support ticket we can get more information via that.
- Kubernetes backup failing due to Node does not have enough resources to get temporary pods created - Once customer reduced the load for the specific worker node the job was able to run and complete without issues
- CMR has been created: 325875 - Optimization logic to be o created from Commvalt side during the provisional resources needed
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.