NW vProxy : vmdk is bigger than the maximum file size supported on datastore
Summary: NW vProxy : vmdk is bigger than the maximum file size supported on datastore
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Case scenario: 2 VMs (VM1 VMDK size 2.5 TB, VM2 VMDK size 3.51 TB) backups failing with Error:
workflow log:
The vProxy /opt/emc/vproxy/runtime/logs/vbackupd/vbackupd-vddk.log
workflow log:
YYYY-MM-DDTHH:mm:SS ERROR: [54] Data Mover: Hard disk 3: VDDK: Failed to open source VMDK '[datastore] vmname/vmname_1.vmdk': VDDK Error: 13: You do not have access rights to this file. Session logs can also be found on the vProxy under: /opt/emc/vproxy/runtime/logs/recycle/vbackupd/
The vProxy /opt/emc/vproxy/runtime/logs/vbackupd/vbackupd-vddk.log
YYYY-MM-DDTHH:mm:SS NOTICE: VDDK INFO 2022-12-12T12:53:13.696-08:00 error -[04369] [Originator@6876 sub=transport] Cannot use mode hotadd to access [vm_datastore] vmname/vmname_1.vmdk: Cannot mount using this method. (Mounting 4204c98e-4fea-b5ba-bbd1-318cc7a24f2c using transport hotadd failed : SupportHotAddTransport: Disk [vm_datastore] vmname/vmname_1.vmdk is bigger than the maximum file size supported on datastore vproxy_datastore_name.)
YYYY-MM-DDTHH:mm:SS NOTICE: VDDK INFO 2022-12-12T12:53:13.696-08:00 info -[04369] [Originator@6876 sub=ThreadPool] Thread delisted
YYYY-MM-DDTHH:mm:SS NOTICE: VDDK INFO VixDiskLib: Unable to locate appropriate transport mode to open disk. Error 13 (You do not have access rights to this file) (Mounting 4204c98e-4fea-b5ba-bbd1-318cc7a24f2c using transport hotadd failed : SupportHotAddTransport: Disk [vm_datastore] vmname/vmname_1.vmdk is bigger than the maximum file size supported on datastore vProxy_datastore.) at 5613.
YYYY-MM-DDTHH:mm:SS NOTICE: VDDK INFO VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [ovm_datastore] vmname/vmname_1.vmdk. Error 13 (You do not have access rights to this file) (Mounting 4204c98e-4fea-b5ba-bbd1-318cc7a24f2c using transport hotadd failed : SupportHotAddTransport: Disk [vm_datastore] vmname/vmname_1.vmdk is bigger than the maximum file size supported on datastore vproxy_datastore.) at 5769.
YYYY-MM-DDTHH:mm:SS NOTICE: VDDK INFO VixDiskLib: VixDiskLib_Open: Cannot open disk [vm_datastore] vmname/vmname_1.vmdk. Error 13 (You do not have access rights to this file) at 5813.
YYYY-MM-DDTHH:mm:SS NOTICE: VDDK INFO VixDiskLib: VixDiskLib_Disconnect: Disconnect.Cause
The error "VM_NAME.vmdk is bigger than the maximum file size supported on datastore" is from the VMware datastore that vProxy is residing on.
Resolution
VMware vMotion/Migrate the vProxy to another datastore in the same cluster, and the backup was successful.
To fix the datastore issue, restarted each of the ESXi hosts in the cluster to obtain a clean connection/mount of all F/C storage. Engage VMware support to investigate the datastore issue further.
To fix the datastore issue, restarted each of the ESXi hosts in the cluster to obtain a clean connection/mount of all F/C storage. Engage VMware support to investigate the datastore issue further.
Affected Products
NetWorkerProducts
NetWorker Family, NetWorker SeriesArticle Properties
Article Number: 000206636
Article Type: Solution
Last Modified: 03 Nov 2023
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.