Plain Virtualization

There are lots of content available nowadays especially with the Broadcom acquisition of VMware, there are many on how to migrate off VMware and feature function comparison. One of the great content that is easily digestible from 2TekGuys . Below is a breakdown from the video on the features that was mentioned available on other hypervisors in comparison with VMware vSphere. I am not going to go into feature beyond mentioned in the video. Here are the list of features mentioned: Load Balancing : Moving using live migration of virtual machines (VMs) between hosts to due to contention. Backup : Support of backup from popular backup vendors or from hypervisor vendor themselves. Storage : Able to utilize external network storage/SAN or hypervisor own hyper-converged storage only. Live Migration : Ability to move VMs without any downtime between hosts. Having specialized on VMware vSphere for a long time in my career and been in a technical role from picking up VMware. I am always amazed by...

With the announcement and also from the datasheet , it seems to be pretty lots of functionalities been added.  However there are some critical ones that are more appealing and wanting to see approvement or resolution to those who are already using since vSphere 4 and prior till today which are not make known to many. Storage There were many discussion over storage UNMAP via thin provisioning and many called it a "myth".  This was also discussed heavily in our Facebook VMUG - ASEAN group.  This was due to many changes since VMFS3 to till VMFS5.  Cody wrote a long history of what are the changes for those who have missed out here . A KB was also release and this create some discussion VMFS3 with different block size would benefit thin provision so to speak before vSphere 5.0 Update 1.  Sadly after which, all UNMAP was not possible via GUI or automatically other than via command line or script. I try to ask internally as well and luckily Cormac with his f...

With many new start ups from storage arrays, converged, hyper-converged to software defined storage (SDS), many users starts to have lots of choice to make. Recently encountering many questions on which should they choose and which is better.  However there is no straight answer as there are just too many choices to choose from just like in a supermarket.  In the end, some may choose one that advertise the best and create the best reminder in your mind.  To be truth, you will not buy and replaced the rest, but rather some have a hybrid environment for some reasons which we will go through later. With several asks and questions, I like to give some guideline when deciding.  Here I will do my best to start with no bias towards any technology and this is my personal opinion and may not be the same with others. 1.  Ease of management: A big word often misused by marketing I would say.  Assess it and ask yourself do you have a team to manage different comp...

I came across some questions by people who were like me who got confused by the new terms of VADP and VAAI or vStorage API. What are these?  How are these related.  The letters do not tell you much so I am doing a explanation here. vStorage API are API also known as application programming interface which are a set of rules or codes given out for any one including vendors or principles to use them and integrate them to produce the function which is provided from the API. In this case, the API has two components: Data Protection Array Integration Do not get confused these two function different things and are meant for different components.  The only similarities is that they allow the function that the API allows to make use of the storage subsystem to lessen the load on the hosts. Lets talk about the two. vStorage API for Data Protection (VADP) In layman terms. This is the API mainly used by backup principles to integrate this function into their software...