Skip to content
Luca Dell'Oca Principal Cloud Architect @Veeam
Virtual To The Core Virtual To The Core

Virtualization blog, the italian way.

  • Media
  • About me
Virtual To The Core
Virtual To The Core

Virtualization blog, the italian way.

The “Real” maximum size of a VMDK file

Luca Dell'Oca, December 3, 2012December 4, 2016

What is the biggest size of a VMDK file?

“2TB – 512 bytes”

This has always been the official answer, and you would find this same answer in blogs, VMware communities, and other sources.

The fact is: this answer is completely correct, but in a “real world environment” is wrong.
No, I’m not going nuts, let me explain.

As I said, the official answer is totally correct, you can create a VMDK that big on any kind of vSphere datastore.
But when it comes to really using that VMDK file, some problems may arise. As you can read in this VMware KB article:

For ESXi 5.0, this error occurs when any individual flat .vmdk file exceeds 2,181,972,430,848 bytes. This is the size generated when adding a virtual disk with size of 1.984492366201720 TB is specified.

ESXi 5.0 is going to check if there is enough free space on the datastore to eventually create a snapshot of that VMDK file, so the actual size of the VMDK file needs to be lower that the official answer. The free space in fact needs to be up to 16 GB for the initial snapshot overhead. Previous version of ESXi did not checked this before creating the snapshot, potentially filling up all the disk and creating problems.

You always have the possibility to redirect the delta files to another disk, but this has some impact on features like sVmotion and Storage DRS.

So, if you need to take a snapshot of that file, probably because you are using VADP libraries to do your backups, you’re better create a smaller disk, and 1.98 TB (or 2032 GB) is the “real” maximum size to be used.

Also, if you wouls like to use a backup software based on VMware VDDK driver and HotAdd mode, please be aware that some tests made by different people has shown this limit is creating troubles, and a safe size is 1.98TB (2027.52 GB). Be careful !

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Pinterest (Opens in new window) Pinterest
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on WhatsApp (Opens in new window) WhatsApp
  • Click to share on Pocket (Opens in new window) Pocket
Tech 2tb5.0VADP

Post navigation

Previous post
Next post

Search

Sponsors

Latest Posts

  • Migrate WSL (Windows Subsystem for Linux) to a new computer
  • Pass keystrokes to a pfSense virtual machine to install it automatically
  • Automatically deploy pfSense with Terraform and Ansible
  • My Automated Lab project: #6 Create a S3 Bucket with Terraform
  • My Automated Lab project: #5 Deploy a Linux vSphere VM with Terraform and custom disks
©2025 Virtual To The Core | WordPress Theme by SuperbThemes
We use cookies to ensure that we give you the best experience on our website, and to collect anonymous data regarding navigations stats using 3rd party plugins; they all adhere to the EU Privacy Laws. If you continue to use this site we will assume that you are ok with it.OkNoPrivacy Policy