VMware Cloud Community
korman
Contributor
Contributor

To VMFS or not to VMFS

I have removed the VMFS partition from my scripted esx build. All my esx hosts are SAN attached and on ocasion someone in error uses the Local partition for a small VM which then becomes isolated and has to be migrated to SAN storage.

When confiiguring a server in my opinion the best practice is to decide to partition /var /tmp /usr , the size is basically arbitrary with the expection of Boot and SWAP. Servers are shipping with 72 GB and 146 GB disks. Another reason to use 3i and save the cost of disks, Raid controllers and the power to run them.

from my ks.cfg

part /boot --fstype ext3 --size 250 --ondisk sda --asprimary

part / --fstype ext3 --size 4096 --grow --ondisk sda --asprimary

part swap --size 1600 --ondisk sda --asprimary

part None --fstype vmkcore --size 94 --ondisk sda

part /var --fstype ext3 --size 4096 --ondisk sda

part /tmp --fstype ext3 --size 4096 --ondisk sda

part /usr --fstype ext3 --size 4096 --ondisk sda

Thoughts?

0 Kudos
6 Replies
Nick42
Contributor
Contributor

Suprised no one replied to this so far. I do agree with you. As part of our build process we do take any disk space left over and format it as VMFS. We never use it, or shold I say, should not use it, but as you said someone does sometimes make that mistake.. Fairy easy to do.

I will look at our process and possibly remove that step in future revisions.

And yea - 3i is the way to go..

0 Kudos
Ken_Cline
Champion
Champion

Moved to the VI3 Strategy and Planning forum

Ken Cline

Technical Director, Virtualization

Wells Landers

VMware Communities User Moderator

Ken Cline VMware vExpert 2009 VMware Communities User Moderator Blogging at: http://KensVirtualReality.wordpress.com/
0 Kudos
Texiwill
Leadership
Leadership

Hello,

There is a use for a local VMFS. Specifically, it is invaluable during one part of your DR/BC plan. That part is what happens if for some reason your remote storage dissappears for some reason. I have seen this happen where a raid array lost drive 1, then while rebuilding it lost drive 2, which meant total array failure. Then while that was being repaired something else catastrophic happened and the whole SAN had to be rebuilt from backup.... That took minimally 48 hours to complete. So during those 48 hours from where will you be running your VMs? SAN/NAS disasters while uncommon do happen and when they do it is pretty bad for everyone involved.

So as a part of my DR/BC process I copy the MOST important VMs from Remote Storage to Local Storage just in case I need to start them up. It saves time on restoring from tape and keeps upper management from breathing down my neck.

This implies however that you do need to maintain vigilance about what is ON those volumes. Perhaps use a VI Perl Toolkit script to shutdown/SVMotion/Monitor those local storage volumes for isolated VMs that are NOT the ones placed there as part of the backup procedure.

Virtualization requires that you increase your vigilance for errors, omissions, and purposeful changes.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354, As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
BUGCHK
Commander
Commander

If you want to prevent somebody else to write into the local VMFS, why not use the old administrator's trick and fill it with a dummy file (vmkfstools -c ...). When you need it, remove the file and enjoy the space Smiley Happy

0 Kudos
mike_laspina
Champion
Champion

Hi,

Local VMFS storage can be useful in the event where you want to redirect heavy vswp file I/O away from the SAN due to performance issues. It's like noise on the SAN if your swapping frequently.

If there are admins using this space and you do not want it to be used you have to ensure that the volume name reflects this idea and it is well communicated. e.g. call the volume Reserved-Localstore-01

http://blog.laspina.ca/ vExpert 2009
0 Kudos
Nick42
Contributor
Contributor

Great discussion!!

It goes to show that there is no right or wrong way to do anything. How you configure your environment must match the needs of the environment, that being done and everything will work as planned and meet expectation.

0 Kudos