https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMDkxIiwiaGFzaCI6IjUwY2Y0Zjk1LTVlZjMtNGUzZi05MTI3LWVhYjcwMTI0YjU4NiJ9
1-800-691-1991 | 9am - 8pm ET
EN

File is larger than the maximum size supported by datastore

Challenge

The following error message occurs when attempting to create a VMware snapshot.

File <unspecified filename> is larger than the maximum size supported by datastore <unspecified datastore>

The Veeam Backup & Replication job fails with the following error:

CreateSnapshot failed, vmRef "vm-xxx", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "False"
File <unspecified filename> is larger than the maximum size supported by datastore

Cause

This error is displayed by Veeam Backup & Replication when creation of a snapshot fails within the user vSphere environment.

The user can recreate this error by manually creating a snapshot on the target virtual machine through the VMware vSphere Client.

KB ID:
1091
Product:
Veeam Backup & Replication
Version:
5.x,6.x,7.x,8.x,9.x
Published:
2011-07-19
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later