Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1281
  • Last Modified:

VMWare: Disk Overhead

Provisioned Space is larger under "Resources" than inside "Disk Provisioning". So how much SAN space is actually needed for a 60GB template?
0
TPG-IT
Asked:
TPG-IT
2 Solutions
 
coolsport00Commented:
You should only need 60GB, plus extra space for the size of the remaining files in the Template folder (.nvram, .logs, etc.). What is the discrepancy amount between the 2?

~coolsport00
0
 
bgoeringCommented:
That kind of depends on how you provision you disk. If you use "thin" provisioning very little space is initially used, but it can grow up to 60GB as you add data to it. If you use any kind of "thick" provisioning you will allocate 60GB for the "flat" file that actually holds the data on the disk, plus just a few bytes (less than 4k typically) for the descripter file. A small amount will also be used for the items listed by coolsport00. When you power on the vm a swap file is created that is the same size as the allocated memory for the vm, so if you have a 4GB vm then a 4GB swap file is created. The size of this file can be reduced by making memory reservation for the virtual machine - but this should only be done if it is absolutely critical the ESX never swap memory contents to disk.

Hope this helps
0
 
TPG-ITAuthor Commented:
If I have a 60GB template, and 12GB of memory, I am really using 72GB of space on the SAN?
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
coolsport00Commented:
Somewhat. It would be 72GB only if it was a VM and was powered on, when swap files become active.

~coolsport00
0
 
bgoeringCommented:
For a template no - but for deploying a vm and then running that vm 72gb would be correct assuming disk was thick provisioned.
0
 
TolomirAdministratorCommented:
I've learned today that it gets a bit more complicated. The SAN volumes that contain the luns also keep snapshots of the luns (which are files at the volume level). So depending on the number of snapshots being taken at the volume level you have to consider additional space needed.

We store our backups in the same SAN where we keep our virtual machines this is the fasted method to create the backups but this also implies that we have only half of the storage available for virtual machines.

0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now