You can easily reach influential IT professionals including decision makers. Talk to us about your products and services and we will do our best to make sure our viewers and readers find you.
Get email updates every time we post!
The recent release of VMware ESX Server 3.5 and VMware Infrastructure 2.5 application updates invokes an urge to try those new features as soon as possible. But as with any major software upgrade, rushing into migration can lead to some major problems, including unplanned downtime. In this tip, I’ll address VMware ESX Server 3.5 upgrade considerations.
Check out this great post talking about upgrading the virtual infrastructure. It raises some great points. I’ve been speaking with colleagues about this, it’s not so much the technical thing, it’s the process, how do we do it? The big bang approach? Do we need to validate the ESX version against our hardware configuration?
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
One Comment
The biggest problems we have encountered in our proposals for upgrading the virtual platform where I am currently working is that many are running ESX 2.5.x and of the systems on the ESX 2.5 HCL quite few have dropped off the VI3 one. So, new hardware but that does give the opportunity to consolidate the platform further.