[merged into existing discussion]
We have been using Veeam Backup and Replication 220.127.116.11 to backup smaller VMs from our ESXi 4 environments to other Windows servers in our LAN. This weekend we did a P2V of a Windows 2003 fileserver to one of our new ESXi installations. The ESXi host has raided internal disks (no shared storage) divided into 2 VMFS datastores. Datastore 1 has a default block size and is 924GB in size. Datastore 2 has a 4mb block size and and is also 924GB in size as it hosts a large 800GB VMDK for this fileserver.
The fileserver consists of 2 VMDKs. The first one is 220GB in size and is the system volume/app store hosted on datastore 1. Datastore 1 has around 556GB free. The second, as mentioned above is 800GB in size and is on Datastore 2 which has 124GB free on it.
When attempting to do a Veeam backup job to a windows share on another server in network mode, the job fails with the following error:
Freezing guest operating system
CreateSnapshot failed, vmRef "vm-422", 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 '<unspecified datastore>
Is this error because there isnt enough space to make the snapshot or because the snapshot veeam is trying to make is too big for the block size of the datastore? If it is the latter, is there any way of getting round the problem without having to trash the datastore and reformat? Or am I going to struggle anyway as I only have 124GB free left on datastore 2? I have already tried doing the backup job excluding the 220GB VMDK and doing the 800GB VMDK on its own. I still get the same error. Any advice would be much appreciated.