- Veeam Support Knowledge Base
- SureBackup fails with “Virtual machine has 4,096 megabytes of memory, which is larger than the maximum 1,024 megabytes supported by the datastore”
SureBackup fails with “Virtual machine has 4,096 megabytes of memory, which is larger than the maximum 1,024 megabytes supported by the datastore”
Get weekly article updates
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
Challenge
A SureBackup job fails to boot a VM in the application group with the following error in a vSphere 5.5 environment:
10/16/2013 2:13:31 PM Getting virtual lab configuration
10/16/2013 2:14:41 PM Starting virtual lab routing engine
10/16/2013 2:15:24 PM DC1 - Publishing
10/16/2013 2:15:30 PM DC1 - Reconfiguring
10/16/2013 2:15:33 PM DC1 - Registering
10/16/2013 2:16:21 PM DC1 - Configuring DC
10/16/2013 2:16:22 PM Error DC1 - Powering on
10/16/2013 2:16:22 PM Error Error: Virtual machine has 4,096 megabytes of memory, which is larger than the maximum 1,024 megabytes supported by the datastore.
10/16/2013 2:13:31 PM Getting virtual lab configuration
10/16/2013 2:14:41 PM Starting virtual lab routing engine
10/16/2013 2:15:24 PM DC1 - Publishing
10/16/2013 2:15:30 PM DC1 - Reconfiguring
10/16/2013 2:15:33 PM DC1 - Registering
10/16/2013 2:16:21 PM DC1 - Configuring DC
10/16/2013 2:16:22 PM Error DC1 - Powering on
10/16/2013 2:16:22 PM Error Error: Virtual machine has 4,096 megabytes of memory, which is larger than the maximum 1,024 megabytes supported by the datastore.
Cause
Your current version of Veeam Backup & Replication is not fully compatible with vSphere 5.5.
Solution
Recreate virtual lab on supported ESX(i) host.
More Information
For vSphere 5.5 compatibility please update to Veeam Backup & Replication 7.0 R2.
Note:
In addition to recreating the virtual lab after updating, you may need to manually unmount the vPower NFS datastore from your ESX(i) host in vSphere Client so that Veeam Backup & Replication can recreate it.
Note:
In addition to recreating the virtual lab after updating, you may need to manually unmount the vPower NFS datastore from your ESX(i) host in vSphere Client so that Veeam Backup & Replication can recreate it.
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.
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.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.