Updating esx server
The Best Practises guide for VMware v Center Update Manager 4.0 ( Manager40_) presents the following guidelines for deployment: You will receive best performance if v Center Update Manager is able to serve the updates from memory rather than disk.Since some of the updates can be significant in size, it is recommended the v Center Update Manager server has 2GB RAM available to cache these updates.In this article we will concentrate on managing v Sphere ESX / ESXi hosts, rather than guests and include some real world experiences of using the tool to manage patching.Patching systems is potentially such a large task that within some organisations there are teams within IT departments who are dedicated solely to this task.Once complete you will also need to install and enable the v Center Update Manager Extension for your instance of the Virtual Infrastructure client – the GUI tool to manage your ESX servers and v Center.Navigate to the Plug-ins menu of your installed VI Client, then Manage Plugins.
The issue with this can be that you will run out of space on your system disk to store all of the patches for the various flavours and versions of ESX / ESXi software.
By default any DSN created on a 64bit system will be a 64bit DSN, so you will need to use the 32bit ODBC Administrator application to create your DSN.
You can then begin the install of v Center Update Manager from the install DVD or ISO.
Imagine a scenario where you install v Center Update Manager whilst you only have version 3.5 ESX hosts, v Center Update Manager will only download patches for that version.
Now add ESXi into your environment and then upgrade to v Sphere 4.0 and typically the amount of disk space required will increase from approximately 5GB to over 15GB – in addition this disk space requirement will always be growing as new patches are downloaded at regular intervals.