Choosing the right partition layout for ESX Servers
WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'and yarpp.reference_ID = 44 AND wp_posts.post_type = 'post' ORDER BY yarpp.scor' at line 1]
SELECT SQL_CALC_FOUND_ROWS distinct wp_posts.*, yarpp.score FROM wp_posts join wp_yarpp_related_cache as yarpp on wp_posts.ID = yarpp.ID WHERE 1=1 AND yarpp.score > and yarpp.reference_ID = 44 AND wp_posts.post_type = 'post' ORDER BY yarpp.score DESC limit 5
- Virtual Infrastructure Best Practices
- Choosing the right partition layout for ESX Servers
- VMWare VI Ports
- Naming Conventions
A lot of stuff has been written about the right partition layout for ESX servers, Leo’s ramblings and VMetc have some information and you will find probably more via google.
As usual it depends what the customer really wants to do with the service console but let’s start with an general idea:
Let’s start with the primary partitions first:
/boot I give it 250 MB to have some space (honestly it is a LOT on the otherside the space is cheap)
/ 8 GB again it is really more than we need normally
swap 1600 MB, so that even if you change the memory for the service console to it’s maximum (800 MB) you have the double amout of swap space
Then we have the extended partitions:
/home 5 GB is the minimum for it if you want to put an dvd iso into your home directory via scp you will need it (yeah, there are still people around which don’t use FastSCP from Veeam)
/var 2 GB
/opt 2 GB
/tmp 2 GB
The later 3 to keep the layout simple, partition var of IS a very needed best practice as it can happen that service console core dump (which go into /var/core) will fill your root partition otherwise. As normally only agents and perhaps their logs go into opt 2 GB is again enough.
Don’t forget
vmkore with 100 MB which is necessary to dump the core dump of the vmkernel if you ever experience a pink screen of death.
And the rest I hear you ask?
Leave it empty! Don’t create a VMFS partition yet. Why? We will talk about that later.
If you don’t want to use the local harddrives for VMFS you are ofcourse able to change the partition layout to accomodate all the space you have, but this is proably in most cases a little bit over the top.
I always find it usefull to store some stuff on the local server, may it be templates or isos, to save some space on the expensive SAN.
Thanks to Leo’s ramblings and VMetc’s primers for validating my ideas.
![Recommend [539]](http://s3.amazonaws.com/arkayne-media/img/logo-recommend-me.png){kind=logo}
Recent Comments