Eco4Cloud Workload Consolidation is a Virtual Infrastructure Optimization Solution designed to improve the economics of virtualized data centers with an intelligent software platform, which increases performances and decreases costs.
Eco4Cloud Workload Consolidation works on top of a virtualization platform, and uses the exposed API to connect to the platform and optimize the workload placement in a virtual farm in order to make it more…
N/A
Hyper-V
Score 8.4 out of 10
N/A
N/A
$24.95
per month
Pricing
Eco4Cloud Workload Consolidation
Hyper-V
Editions & Modules
No answers on this topic
Developer
$24.95
per month
Bronze
$49.00
per month
Silver
$89.00
per month
Gold
$135.00
per month
Platinum
$199.00
per month
Offerings
Pricing Offerings
Eco4Cloud Workload Consolidation
Hyper-V
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Eco4Cloud Workload Consolidation
Hyper-V
Features
Eco4Cloud Workload Consolidation
Hyper-V
Server Virtualization
Comparison of Server Virtualization features of Product A and Product B
Eco4Cloud is well suited in VMware farms that have standard VM deployments, especially with small VMs, with nothing blocking vMotion and hardware fully compatible with IPMI 2.0 (minimum). It doesn't work well if many VMs are nodes in a Microsoft cluster because they would be unmovable and therefore their host would never be put in stand-by mode. If every host in the cluster has at least one guest VM that is a node of a Microsoft cluster, no host in the cluster will ever be put in stand-by mode.
If budgets are stretched, Hyper-V is a very cost effective solution. Any veteran MS Windows administrators will have little issue in getting to grips with this. If you are familiar with VMware solutions, then you may find Hyper-V a little frustrating as it does lack some of the functionality of those products, however nothing that will prevent you from managing your virtual workloads and estate. Since rolling out Hyper-V 2019 we have had no real issues with it; ESXi seemed to have more issues and was less forgiving with hardware compatibility.
It consolidates workloads in VMware clusters using an algorithm that seems to work better than VMware DRS. It keeps headroom for workload peaks and to withstand the number of host failures set for the cluster in vCenter.
If the workload is very variable, Eco4Cloud will not continuously turn a host on and off but it will settle to keep the host running. It sort of "rightsizes" the cluster keeping only the right number of hosts running. This is another main difference when comparing Eco4Cloud with VMware DRS/DPM which strictly follows the workload and sometimes isn't fast enough in turning on the hosts when the workload is ramping-up.
To do a good job Eco4Cloud needs to analyze the hosts and the VMs. Therefore, the troubleshooting component of Eco4Cloud can figure out if there are problems in the configuration of the hosts (e.g. vMotion settings). It can also determine if a VM is stuck and can't vMotion (e.g. using the physical CD-ROM) or if it's oversized or undersized.
Something Eco4Cloud has and others don't is a technology named Smart Ballooning. With Smart Ballooning Eco4Cloud recovers unused RAM from the VMs and gives it back to the host way before the host goes over the 94% RAM threshold. This allows us to reach higher levels of overbooking.
Easy to use GUI - very easy for someone with sufficient Windows experience - not necessarily a system administrator.
Provisioning VMs with different OSes - we mostly rely on different flavors of Windows Server, but having a few *nix distributions was not that difficult.
Managing virtual networks - we usually have 1 or 2 VLANs for our business purposes, but we are happy with the outcomes.
The only issue I have with Hyper-V is I am unable to use Veeam on my Windows 2016 Server to backup my FreeBSD HAProxy VM.
There is some sort of checkpoint issue that I have been unable to figure out, but it works just fine on my Windows 2012 Servers. I do believe this is a Microsoft issue and not a Veeam issue though.
Another thing that could be useful that Hyper-V does not have would be some sort of GUI that shows the status of all the VM's on a given server to help us manage them easier and know what is going on. However, I do have Zabbix for this and that does a good job at monitoring all my servers.
Cheap and easy is the name of the game. It has great support, it doesn't require additional licenses, it works the same if it is a cluster or stand-alone, and all the servers can be centrally managed from a system center virtual machine manager server, even when located at remote sites.
It is very easy to configure new virtual machines and manage them. But you have to use different interfaces to perform various tasks. Especially as soon as it comes to clustering you have to use at least two different interfaces (Hyper-V Manager and Failover-Cluster Manager) to perform all necessary tasks. The newly released Windows Admin Center is a way into the right direction to get all management tasks into one single interface.
In the past 2 years our Hyper-V servers have only had a handful of instances where the VM's on them were unreachable and the physical Hyper-V server had to be restarted. One time this was due to a RAM issue with the physical box and was resolved when we stopped using dynamic memory in Hyper-V. The other times were after updates were installed and the physical box was not restarted after the updates were installed.
Hyper-V itself works quickly and rarely gave performance issues but this can be more attributed to the physical server specifications that the actual Hyper-V software in my opinion as Hyper-V technically just utilizes config files such as xml, and a data drive file (VHD, VHDX, etc) to perform its' duties.
Hyper-V is greatly supported by techs around the world. There are tons of forums, help websites and individuals ready to answer questions. I've never needed to contact Microsoft for help...because help is so easy to find out there. Do a search online for anything related to Hyper-V and you will certainly find an article with spelled out steps on how to do what you are looking to do.
We had in person training from a third party and while it was very in depth it was at a beginner's level and by the time we received the training we had advanced past this level so it was monotonous and redundant at that point. It was good training though and would have provided a solid foundation for learning the rest of Hyper-V had I had it from the beginning.
The training was easy to read and find. There were good examples in the training and it is plentiful if you use third party resources also. It is not perfect as sometimes you may have a specific question and have to spend time learning or in the rare case you get an error you might have to research that error code which could have multiple causes.
initial configuration of hyper-v is intuitive to anyone familiar with windows and roles for basic items like single server deployments, storage and basic networking. the majority of the problems were with implementing advanced features like high availability and more complex networking. There is a lot of documentation on how to do it but it is not seamless, even to experienced virtualization professionals.
We compared the consolidation feature and we obtained exactly the same amount of servers in stand-by. The main difference was that Eco4Cloud turned off the unneeded hosts in 2 days while VMTurbo Operations Manager required one day per host. This behavior is caused by the different algorithms implemented by these two products. Compared to Eco4Cloud, VMware DRS/DPM was very aggressive (we tried it in vSphere 5.0). We haven't tested it with vSphere 6 yet.
VMware is the pioneer of virtualization but when you compare it with Hyper-V, VMware lacks the flexibility of hardware customization and configuration options Hyper-V has also GPU virtualization still not adequate for both platforms. VMware has better graphical interface and control options for virtual machines. Another advantage VMware has is it does not need a dedicated os GUI base installation only needs small resources and can easily install on any host.
Nothing is perfect but Hyper-V does a great job of showing the necessary data to users to ensure that there is enough resources to perform essential functions. You can also select what fields show on the management console which is helpful for a quick glance. There are notifications that can be set up and if things go unnoticed and a Hyper-V server runs out of a resource it will safely and quickly shut down the VM's it needs to in order to ensure no Hardware failure or unnecessary data loss.
Hyper-V has provided for an extremely cost-effective virtual environment with disaster recovery. For the size of our business, it's all we need to ensure our desired level of continuity of services and protection against hardware failures.
Since we are a Windows shop, deploying Hyper-V means we don't have the added cost of a hypervisor, since it's included in the cost of the Windows Server license. It's all we needed to achieve our goal of running all our virtual machines on a single server with another, less expensive server on tap for replication and failover.
We wanted easy deployment and management with disaster recovery while having the ability to leverage our years of Windows SysAdmin experience. Hyper-V fit the bill.
