Veeam Support Knowledge Base
Veeam Kasten for Kubernetes - vSphere Block Mode Exports Failure With Error 14009

Veeam Kasten for Kubernetes - vSphere Block Mode Exports Failure With Error 14009

KB ID:	4615
Product:	Veeam Kasten for Kubernetes
Published:	2024-06-12
Last Modified:	2024-06-12

By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please, try again later.

Challenge

During vSphere block mode export, in certain situations, it might be observed that the folders/objects get created in the storage bucket. However, the export job remains stuck, and the following error message is seen in the debug logs:

"Open virtual disk file failed. The error code is 14009., try --help\nError: exit status 1"

Veeam Kasten for Kubernetes requires network access from the cluster to vCenter and the ESX hosts in TKGs environments.

Solution

Verify Environmental Configuration

Check firewall configuration - port 902 should be open between worker nodes to the ESX nodes.

kubectl run -i --tty busybox --image=busybox:1.28 -- sh 
telnet <esxhost name> 902

In addition to error 14009, if error 3014 is seen, check if the vSphere account used to create the Infrastructure Profile has sufficient permissions to create a disk/snapshot in the vSphere console.

Check if the ESX host can be reached using the DNS name. Sometimes, if the ESX server cannot be resolved using DNS, it throws error 14009.

ping <ESX Host Name>

Adjust KanisterBackupTimeout

If the job runs for some time and then 14009 errors are seen, it may be due to the kanisterbackup timeout. By default, this is set to 45. Try increasing the "KanisterBackupTimeout" value to longer than 45 minutes, for example, to 600 minutes.

helm upgrade k10 kasten/k10 --namespace=kasten-io --reuse-values -set kanister.backupTimeout=600
                
            

More Information

In some cases, it may be observed that the data-mover pod does not initiate, and the log shows 14009 errors. Further troubleshooting to find why the data-mover is not initiating is recommended in these cases.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Verify your email to continue your product download

We've sent a verification code to:

An email with a verification code was just sent to

Didn't receive the code? Click to resend in sec

Didn't receive the code? Click to resend

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.