Posts

Showing posts with the label migrate

Lock In or Not

Image
The term "lock in" has been there for many reasons. Recently was in a discussion with some customers and this term came about again. Let's first define "lock in". In the context of IT, "lock in" prevent customers from moving away from an adopted technology, or you call in trapped. Using example of mainframe. Once an application runs mainframe, there is no alternative replacement. The only way to move out is to look for a replacement doing a complete refactor and hoping that data can still be utilised. That also explains, in the early days when mainframe was introduced till date, most are still on it. Also of course not mentioning the reliability and downtime that mainframe provide. At that point in time, there were only less than a handful of mainframe system e.g. IBM, Compaq Tandem, etc. and the technology offered were far beyond any others. At today's context, technology choices of a similar domain are massive. Even though mainframe might be an l...

Upgrade from vSphere 4.x to vSphere 5

Have visited several customers and everyone is on different version of vSphere 4.x update and some on vSphere 5 (that is good) and some are still in VI3.5. Many are not considering to do further upgrade but intend to migrated directly to vSphere 5.  The good news is the upgrade can be in place upgrade by using the CD or simply use the vCenter Update Manager. However there are some issues arised for specific versions of vSphere 4.x which need to be take care of  before doing the upgrade/migration to vSphere 5 else you might just lose the environment. Users who are on vSphere 4.0 Update 2: ESXi 4.0 hosts may experience a purple screen after vCenter Server is upgraded to 5.0   Resolution: In vCenter 5.0 Update 1  vSphere 4.1: After upgrading from vCenter Server 4.1 to 5.0, the ESX/ESXi 4.1 host fails with the PSOD error: Spin count exceeded (VASpace) - possible deadlock with PCPU 2 Resolution: Upgrade to ESX/ESXi 4.1 Update 1 befor...