CTERA Edge X Series (discontinued) vs. Eco4Cloud Workload Consolidation

This is all about the selling you a "Device" and prices vary greatly between resellers. The devices work well, but the pure cloud solutions need a lot of work.

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.

• Standard File Backup

• 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.

• SQL Backups just don't work reliably. For us, we lost all of our SQL data backed up through the CTERA Application process. Although the logs indicated a success, that was really not the case. This came close to putting us out of business. Luckily I had taken a genuine SQL backup to a folder. Unfortunately it was a month old. We had to pick-up the pieces from there.
• Don't use it for file sync and share. There are better products out there i.e. anchorworks.com
• Support sucks. Good luck with response time and answers that are inconsistent between team members. For example I had to rebuild a VM from scratch. When I re-installed the CTERA client It obviously thought I was adding another device. When I inquired to tech support, one member said "copy the old Data folder" (I still had the old VHD. That did not work). The other directed me to the correct spot to just change the associated folder. The turn-around time was over 24 hours for this simple fix.
• Documentation, plenty of fodder but no real tech there.

• It would be useful to have a version that works with OpenStack.
• It should be made compatible with VMware VSAN.
• It would be useful to have a version that works with hybrid clouds using the new "vMotion anywhere" or share nothing vMotion feature.

Unfortunately CTERA does not stack up well if you want a pure cloud BDR. I have use iDrive and Asigra. iDrive has similar support and SQL backup issues. Asigra can vary widely in support and price, but the software is solid.

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.

• NONE, it about put us out of business

• Eco4Cloud causes a reduction in power consumption both on old VMware clusters and especially on new ones.
• It also causes a delay in CapEx investments because you buy more hosts only when really needed.