In-depth ESX Server service console partitioning and provisioning

The recommended partitioning scheme I described came from some documentation that VMware makes available to their VMware Authorized Consulting (VAC) partners. Before reviewing that documentation, I had developed my own service console partitioning scheme based on my knowledge of ESX Server and experience in the field installing the product. The partitioning scheme that I had developed looked something like this:

[TABLE]

The basic rationale behind this scheme, which I would imagine is very similar to schemes developed by fellow engineers who install ESX Server on a regular basis, boils down to protecting the root partition from filling up:

After reviewing the VAC Partner documentation and looking at the recommendations, and reviewing the space utilization on some of our previous installations, I developed this new partitioning scheme:

[TABLE]

The changes from the original scheme are based on the size of the swap partition and some of the extended partitions. The reasoning behind the swap partition's change in size has to do with the amount of memory given to the service console. The recommended swap space for the service console is eq

Digg This!     StumbleUpon     Del.icio.us

More memory may need to be allocated to the service console if additional software packages—such as a hardware management agent or a backup agent--and ESX Server can allocate up to 800MB of RAM. By setting the swap size to 1600MB we guarantee that enough swap size has been set, regardless of the amount of RAM allocated to the service console.

Similarly, the recommended sizes for /tmp and /home ends up being smaller as fewer and fewer software packages install themselves into /home. Instead, they install themselves into /opt, warranting its own partition. The VMware HA agent is one example of software that installs itself into /opt.

Of course, any partitioning scheme for ESX Server's Service Console needs to be tailored to that organization's specific needs, but this scheme provides a good starting point for designs and for discussions with the customers about their needs.

ABOUT THE AUTHOR: Scott Lowe is a senior engineer for ePlus Technology, Inc. He has a broad range of experience, specializing in enterprise technologies such as storage area networks, server virtualization, directory services, and interoperability. Previously he was President and CTO of Mercurion Systems, an IT consulting firm, and CTO of iO Systems.

Rate this Tip To rate tips, you must be a member of SearchVMware.com. Register now to start rating these tips. Log in if you are already a member. DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.