Skip to main content

David's advice: Plan wisely before moving to ESX 3.5

Upgrading ESX Server involved upgrading the related applications in the VMware Infrastructure Suite at the same time. Single VMware ESX Server upgrades minus VMware Infrastructure Suite applications require users to upgrade the ESX Server OS to 3.5, followed by a VMware Infrastructure client to version 2.5 upgrade.

However, most of us don't have such a simple configuration. Real VMware ESX Server production environments may consist of any number of ESX Servers, a VMware VirtualCenter Server, a VirtualCenter database, VMware License Server, VMware Consolidated Backup (VCB), VMware Tools in the Guest VMs, and the VI Clients.

Though upgrading a single ESX Server from 3.x to 3.5 is relatively straightforward, having so many different pieces across the entire VMware Infrastructure Suite installation adds complexity to upgrades. For that reason, the pitfalls I list out below have to do with not only upgrading VMware ESX Server but also the entire VMware Infrastructure Suite. A particular problem is that some settings in the local Linux Service Console may be unexpectedly modified, so it's a good idea to test systems before upgrading

Servers that run VMware ESX are usually powerful and expensive. So developing a group of test systems comparable to the "suite" of systems working together in your VMware Infrastructure can be difficult. An excellent way of doing this is to run VMware ESX Server on a small server that marginally meets the hardware requirements while running VMware VirtualCenter in a virtual guest OS on one of your existing servers. This configuration allows you to perform a number of tests before doing the real upgrade on the production network.


Link
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op...
Post a Comment
Read more