- Veeam Support Knowledge Base
- Failed to write data to the file *.vbk - file too large
Failed to write data to the file *.vbk - file too large
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
Cause
The file system or operating system of the Linux repository does not support the size of the backup file.
The maximum file size on a particular repository server depends on a number of factors and can vary with block size, between kernel versions, and between versions of a file system. For example, SLES 11 32-bit has a kernel-based file size limitation of 2 TiB. Older kernels or distributions that lack large file support may have a file size limit as small as 2 GiB.
File system limitations encountered by typical jobs include:
If you have specified an ESX 4.x host as a Linux repository, the following limitations apply:
The maximum file size on a particular repository server depends on a number of factors and can vary with block size, between kernel versions, and between versions of a file system. For example, SLES 11 32-bit has a kernel-based file size limitation of 2 TiB. Older kernels or distributions that lack large file support may have a file size limit as small as 2 GiB.
File system 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 |
| Ext4, 1KiB block size | 4 TiB |
| Ext4, 2KiB block size | 8 TiB |
| Ext4, 4KiB block size | 16 TiB |
If you have specified an ESX 4.x host as a Linux repository, the following limitations apply:
| File System | Maximum File Size |
| VMFS3, 1KiB block size | 256 GiB |
| VMFS3, 2KiB block size | 512 GiB |
| VMFS3, 4KiB block size | 1 TiB |
| VMFS3, 8KiB block size | 2 TiB minus 512B |
Solution
To resolve this issue, you can do any of the following:
- Copy any files currently on the repository to another storage device, then reformat the disk with a file system that supports larger files, such as XFS.
- Replace the operating system of the 32-bit Linux repository server with 64-bit Linux (if applicable).
- Point the job to a repository that supports larger files.
More Information
Please see the following VMware Knowledge Base article for more information about block size requirements:
http://kb.vmware.com/kb/1003565
http://kb.vmware.com/kb/1003565
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.