Back in April I wrote a blog aimed and the differences between ESX and ESXi. The original post was written for ESX 3.5 and with the introduction of vSphere I think it’s about time i have revisited this topic and looked at the pros and cons of ESX4 and ESX4i. Now before we dig into the technical details there is one big thing you should all be aware of. The FAQ page published by VMware states “VMware ESXi is the recommended platform for both new and existing customers. Future hypervisor releases will solely be based on this architecture.”
For most that should be enough said. After reading that I would seriously start rolling out ESXi in a lab and start figuring out how I could maintain my needs without the service console most of us have become to know and love. I would also start brushing up on the RCLI as well as the PowerCLI if you are currently dependent on scripts that run in the service console. The good news is almost everything you do today in the service console can be achieved one way or another with ESXi as well. OK with that said lets talk about some of the other limitations.
Read more…
Share on Facebook
Categories: Cloud Computing, ESX 4, Other, VMware, networking, storage Tags: Cloud Computing, Desktop Virtualization, ESX4, ESXi, vCenter, VI4, virtualization, VMware, vsphere
VMware SRM is gaining a lot of traction and many companies are quickly making it the defacto choice for DR in their environments, but is SRM the right choice? For those of you who haven’t had the opportunity to get familiar with SRM (Site Recovery manager), it is a Disaster Recovery automation product from VMware that integrates into vCenter. Through the use of SRA’s (Storage Replication Adapters) SRM is able to integrate with many storage arrays making it aware of Datastores that are replicated. Some of it’s most popular fetures include the ability to group servers in to recovery groups giving you the ability to fail groups of servers or a whole datacenter. It also allows you to perform live failover tests on the the same groups of servers or an entire site. These are some of the most popular reasons companies are implementing SRM. The ability to easily run DR tests without impacting live running systems has made it a huge success. SRM also allows you to create DR run book automation through the use of linear workflows that you create to perform different steps and tasks involved with failing over from the primary site to a secondary.
All of this is great stuff right? What could possibly be better that this? What can’t SRM do?
Read more…
Share on Facebook
Last Month, I attended a Brocade Net.Ed Session that covered Converged Enhanced Ethernet (CEE) and Fibre Channel over Ethernet (FCoE) and the idea of Server I/O Consolidation. If you missed the Net.Ed sessions, you can learn about it at Brocade’s Training Portal. Once you register / login, click on Self-Pased Training and search or browse for FCoE 101 Introduction to Fibre Channel over Ethernet (FCoE). It’s free. Here is an unabridged report about the Net.Ed session with some of my opinions wrapped in:
Trends
Read more…
Share on Facebook
Just thought I would share these diagrams that I used in a recent training session. I used them to explain the differences in the storage protocols that may be used for a vStorage Cloud and how FCoE works. Click on the images for a larger view.
Read more…
Share on Facebook
Yes folks, it rears its ugly head again…Disk Alignment… If you have not read it yet, check out the whitepaper on disk alignment from VMware.
First, chethan from VMware posted a great thread on VMTN about I/O performance in vSphere. The start of the thread talks about I/O, then leads into anice discussion about block size. A couple of weeks ago, Duncan Epping posted a very informative article about block sizes. It convinced me to use 8MB blocks in VMFS designs.
Read more…
Share on Facebook
