Backup Failure Stating Not Enough Storage

[rgs3]

I keep getting these backup failures stating that there isnt enough storage, however there are over 7TB of space available.
Anyone know why I'm getting this? I'm backing up to a server share via VA mode. This just started happening a few days ago. I put the VM summary below.


Total VM size: 273.40 GB
Processed size: 12.74 KB
Processing rate: 0 KB/s
Backup mode: HOTADD with changed block tracking
Start time: 5/5/2010 9:00:53 AM
End time: 5/5/2010 9:05:18 AM
Duration: 0:04:25

Backing up file "[NFS_SAS01] Server01/Server01-flat.vmdk"
BackupDisk failed
Client error: Not enough server storage is available to process this command
Failed to write data to the file [\\BU01\backup\vmware\veeam\Production Backup.vbk].

Server error: End of file

[Gostev]

Hello, I believe this could be the issue documented in the Release Notes:

• If ESX datastore hosting Veeam Backup VM has less free space than biggest virtual disk of backed up VM, Virtual Appliance mode fails with the insufficient disk space error.

[rgs3]

Hi Gostev, Thanks for the reply. However, the datastore hosting the Veeam backup VM has 1.33TB free space available. My biggest disk is 1TB and the job fails on multiple VMs with much less disk space, for example the one in my first post has a total size of 273GB.

[Gostev]

Can you try to create the same job, but backup to a different location, and see if the issue is still there? This would help to isolate the issue and understand whether it is related to specific target storage you are using to write backups to. Also, what is your support case number, if you have one open?

[rgs3]

Sure, Ill try to backup to a different location.
No support case number, I dont have one open. We are evaluating backup products and using the trial.

[Gostev]

We do provide support for evaluators with active trial license, so no problems here. Please open a support case by sending all logs from Help | Support information to support@veeam.com. Most issues can be understood by just looking at those debug logs. Much more info there than in session's summary.