I only know what I know...which is my IT world. Having two datacenters that were physical servers attached to a SAN that "attempted" to replicate and then migrating. For a SMB small IT shop that happens to have two datacenters already in place...this has been ideal. I can have a generalist maintain the system and we have a private cloud for DR with hardly any effort...the biggest gain by far!
Hyper-V makes a lot of sense in scenarios that will support several Windows Server-based OS virtual machines. The only limitation of those licensed VMs is the hardware that hosts the Hyper-V role. If you need to deploy many servers running Windows Server OS, it is worth the price. Hyper-V also does a great job of managing the server host's computational resources, including memory, CPU, network, and storage.
Deduplication and Compression - SimpliVity keeps the space consumption to a minimum. We currently have 60 servers running virtually and we still have room to grow. This really helps with the backups as we can have longer retention.
Backups - Ability to keep backups for longer and to create multiple backup policies for a VM is a breeze. You can have a backup policy for each datastore as well as a separate backup policy for the same VM.
Creating Datastores is very easy. No more messing around with LUNS and iSCSI. Just go to the SimpliVity tab and select create datastore and it's done. You can also increase the datastore on the fly as well as have a datastore bigger than 2TB.
File level recovery is included as well. The whole backup process in SimpliVity can help you do away with other software.
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.
We manage Hyper-V using both System Center Virtual Machine Manager (SCVMM) and the in-build Hyper-V administration tool, the former being the main product we use as the built-in tool is very light on functionality, unlike VMware ESXi.
Management of storage is not great and quite a shift away from how VMware does it with ESXi; there is no separate panel/blade/window for LUNs/data stores, which means there is a lot of back and forth when trying to manage storage.
A dedicated client with all functionality in one place would be awesome.
Having the equivalent of ESXi's virtual console is something which is absolutely needed.
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 sits nicely ontop of VMWare and is easy enough to use. Some improvements to the UI could be done, such as placing buttons where it is expected to have them not in unusual places, so you have to hunt for them. The backup and restore is intuitive and makes things super easy if you need to do a quick rollback. Space savings on multiple VMs and backups means we are backing up more than we need which gives us confidence in what we do. Updating the system is also fairly easy and their support has always been fantastic. They will contact us if they detect any issues, usually before we notice them!
It is quite intuitive. Junior techs are able to provision and administrate Hyper-V virtual server infrastructure with little to no additional training. Documentation from Microsoft is easily avaliable and decently well written. Hyper-V is reliable and does what it is supposed to. Can be admin from an intuitive gui, or aoutmated with extensive powershell.
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.
Support is very good. With proactive support, you are supported by an engineer in North America who answers the phone and immediately begins assisting with your issue. The folks I have dealt with in the last several years have been very skilled and it is rare to have a ticket open for more than a day or two. Issues affecting production are dealt with appropriately and are escalated within the support organization.
I gave it a middle of the road rating - as far as getting direct help from Microsoft this never seems to happen. (Good luck getting ahold of them.) Getting help from online support forums is pretty much where I get all my help from. Hyper-V is used quite widely and anything you could need help with is out there and easily searched for on your favorite search engine.
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.
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.
HPE SimpliVity provided us with the ability to replace our existing infrastructure with a solution that provided better backup and recovery, and an off-site DR solution, at a lower price point than other solutions.
Massively positive impact on expenses in my company by reducing our storage needs drastically. We were able to reallocate the budget to upgrading our primary Hyper-V server with pure enterprise SSD's as we reduced the storage needs by over 50% and by this we increased performance by over 400%.
We have deployed more than 8 servers with EXTREMELY minimal cost using Hyper-V and not requiring another hardware server to host it. We have leveraged our hardware resources in our 2 servers so well that we were able to add many new services, not in place prior, as we did not have the servers to host them. Now with Hyper-V, we deployed many more servers in VM's, purchased OS's & CAL's, but did not need any hardware, which is the greatest expense of all.
With Hyper-V, our ROI was reduced from 36-40 months on our primary server, down to only 13 months by reducing costs of storage and adding so many more servers, by calculating the "would-be" cost of those servers that was avoided by creating them in Hyper-V.
