Virtualization Team

I have seen tons of articles talking about the differences between VMware ESX & VMware ESXi, but I have not seen many that discuss when to use them. I have noticed that many of my customers get even more confused when reading comparisons between the two, as not all of them have deep understanding of the Virtualization Technology. That means they got to know the differences, but still wondering which one is best fit for their environments. Below is few rules that can put you on the right path.

After a week of testing and fuzzing with both VizionCore vReplicator originally known by esxReplicator as well Veeam Backup & Replication, I was able to be one of the contributor to the new comparison at ITComparison.com.

The comparison titled VizionCore vReplicator (esxReplicator) vs Veeam Backup & Replication covers many important aspects of the two products. It has been well crafted to help IT professionals find out which product is better for their enviornment. I was glad all this collaboration with other virtualizaiton professionals has met up with success & the comparison was released to the public yesterday.

I have a great news today from VMware. They have released the new version of VMware Site Recovery Manager SRM which will support VMware vSphere. This release of SRM had been long waited by many of us who upgraded, or already planning to upgrade to vSphere. I thought I will share the good news with every one.

The support for vSphere is not everything, but another great feature of the new SRM is the ability to support multiple source to a single target storage, which was not supported by earlier releases of VMware.

Another long waited feature for SRM is the support for NFS Datastores. Yes, finally NFS is supported by VMware Site Recovery Manager.

I have been hearing many IT Professionals on many forums on the web complaining that their DHCP Server which is setup at the parent partition of their MS Windows 2008 Hyper-V Server is not working. Further more many of them has reported an error similar to the below one in their error logs:

1041:
The DHCP service is not servicing any DHCPv4 clients because none of the
active network interfaces have statically configured IPv4 addresses, or
there are no active interfaces.

The first thing I would like to bring to these administrators attention & to everyone else trying to setup any services or application in the parent partition of Hyper-V to consider avoiding that if possible at all cost. As its not recommended and almost not supported to use the parent partition for serving roles & services beside the Hyper-V role.