Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
VMware VM Backup Failure with Internal 65535 Error: "Cannot Concatenate 'str' and 'NoneType' Objects"
VMware VM Backup Failure with Internal 65535 Error: "Cannot Concatenate 'str' and 'NoneType' Objects"

VMware Backup Failure with Internal 65535 Error: "Cannot Concatenate 'str' and 'NoneType' Objects"

Updated yesterday

Problem Description

This article explains the error message "cannot concatenate 'str' and 'NoneType' objects" encountered during VMware backups in Druva, its root cause, and the steps to resolve it.

Traceback:

[2024-11-22 18:51:33,327] [INFO] Checking job status...

[2024-11-22 18:51:45,333] [INFO] VMX fpath: [NetApp_nfs_ds2] FASCCH13/FASCCH13.vmx

[2024-11-22 18:51:45,334] [ERROR] Error <type 'exceptions.TypeError'>:cannot concatenate 'str' and 'NoneType' objects. Traceback -Traceback (most recent call last):

File "agents/vmware/vmwareAgent.py", line 1772, in do_retry

File "agents/vmware/vmwareAgent.py", line 1958, in get_nvram_from_datastore

File "agents/vmware/vmwareAgent.py", line 1945, in __get_nvram_path

TypeError: cannot concatenate 'str' and 'NoneType' objects

Cause:

This error occurs when the Druva VMware Agent tries to construct a file path but one of the components (such as the NVRAM file path or VM configuration details) is missing or returns as None. The root causes are typically:

  • Inaccessible or unmounted datastore.

  • Corrupted or missing VM configuration files (e.g., VMX files).

Resolution:

Steps to Check and Resolve on vCenter:

  1. Verify that the VM referenced in the error log (e.g., FASCCH13) exists and is accessible in vCenter or the ESXi host.

  2. Ensure the datastore ([NetApp_nfs_ds2]) is mounted and accessible.

  3. Check the VMX file path mentioned in the log (FASCCH13/FASCCH13.vmx) for any corruption or missing files.

  4. If issues persist, perform a vMotion or migrate the VM to a different host within the same vCenter.

  5. Re-run the backups after confirming the VM and datastore are accessible.

If the issue continues, reach out to Druva Support for further assistance.

See also

Did this answer your question?