Hot-Add job failing with "3201: Can't Read [datastore]<vmname>\<vmname>.vmdk" (4043507)

Hot-Add job failing with "3201: Can't Read [datastore]<vmname>\<vmname>.vmdk"

If vRanger is not on a datastore not created as VMFS5, Make sure that vRanger is on a datatore that is large enough to support the vmdk size that is trying to be mounted.

Below is the file size maximums for pre-VMFS5 created datastores that are allow in these datastores:

• 1MB - 256GB
• 2MB - 512GB
• 4MB - 1024GB
• 8MB - 2048GB

You can find the block size of a datastore by the following procedure:

1. Iin the vSphere client, by navigating to the vRanger machine and on the summary tab take note of the "Host" and "Datastore" Entries.
2. Select the host that vRanger is located and navigate to the "Configuration" tab.
3. Then Select "Storage" on the left side
4. Select the datastore is located on and below the configuration of that datastore should show up.
5. Match the block size to the table from above and determine if the largest HDD of the VM that is failing is larger then the block size maximums
6. If the HDD is to large, then you will need to migrate the vRanger server to a larger block size datastore.

Migrating to Another Datastore

1. Right-click the vRanger VM and select "Migrate"
2. Select "Datastore" and press 'next'
3. Select the Datastore that has a larger Blocksize and press Next and Finish
4. Run the job again to see if that fixes the issue.