"Virtual machine has ‘X’ megabytes of memory which is larger than the maximum ‘X’ megabytes supported by the datastore.”

Veeam Backup & Replication
7.x, 8.x
Last Modified:


Error "Virtual-machine-has-X-megabytes-of-memory-which-is-larger-than-the-maximum-X-megabytes-supported-by-the-datastore" can occur with Other OS FLR, Instant Recovery, or SureBackup.


Assuming the VeeamBackup datastore is present and not being used the first troubleshooting step for this error should be to Unmount the VeeamBackup datastore and then try again the tasks that threw the error.

Below are the three most common causes of this issue and their respective resolutions.
Cause 1:
This occurs when you manually select a resource pool for a Veeam component and the resource pool does not have enough memory allocation to accommodate this VM

Resolution: Increase the memory allocation to the resource pool or do not use a predetermined resource pool and use the top tier ‘Resource Pools’ and let it self assign.

Cause 2:
This can occur when restoring a VM, including SureBackup, that was backed up with Veeam Backup & Replication version or older, to a vSphere 5.5 environment.

Resolution: This configuration is unsupported, any restores from this cannot be guaranteed. It is advised that you install the most recent patch. http://www.veeam.com/patches.html

More information regarding resolving this error when it occurs during SureBackup can be found at www.veeam.com/KB1826.

Cause 3:
A similar issue can occur if the NFS datastore location/location you specified for Virtual Lab does not have enough free space to create the swap file.

Resolution: Investigate and resolve any free space issues that may be occurring.



Rate the quality of this KB article: 
4 out of 5 based on 4 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: