#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
BACK TO KB LIST

There Is Not Enough Space on the Disk

KB ID: 1827
Product: Veeam Backup & Replication
Published: 2013-10-25
Last Modified: 2023-11-14
mailbox
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

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

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

A job or task reports the error:

There is not enough space on the disk

Cause

This error is relayed by Veeam Backup & Replication when the underlying system reports the error while attempting to write a file.

More often than not, this error quite literally means the disk has insufficient free space.

However, if it can be determined that the disk Veeam Backup & Replication was attempting to write to has sufficient free space, the issue may instead be related to a filesystem limitation or a configured disk quota. File system limits, file system quotas, or network share quotas can trigger this error.

  • If the error is due to a file size limit, the job will always fail after transferring the same amount of data.
  • If the error is due to a quota, subsequent job sessions will typically fail without transferring any data.

For example, a job fails with the following details in the report:

Error: Client error: An existing connection was forcibly closed by the remote host Exception from server: There is not enough space on the disk. Failed to write data to the file [D:\Backup\VM Backup\VM Backup2013-10-05T183834.vbk]. Failed to perform data backup.

In this example, the job always failed each time the .vbk file reached 4 GiB, but the storage device had over 1TB free. It was formatted as FAT32.

Limitations encountered by typical jobs include:

File System Maximum File Size
FAT32 4 GiB
Ext3, 1KiB block size 16 GiB
Ext3, 2KiB block size 256 GiB
Ext3, 4KiB+ block size 2 TiB

Other file system limitations may be encountered by unusually large backup jobs.

Solution

  1. Identify what file Veeam Backup & Replication was attempting to create/write when the error occurred.
  2. Check if that disk has sufficient free space.
  3. Check if there is a filesystem single file size limitation.
  4. Check if a disk quota is configured.

More Information

TechNet: NTFS Disk Quotas

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.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
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!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.