Next stop for your virtualization needs - VMware's vSphere client and server
November 08, 2016

Next stop for your virtualization needs - VMware's vSphere client and server

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with vSphere

I worked for Cisco systems in Boxborough. And it is currently used by a specific number of users who i provide maintenance of vSphere to. They use it to host their virtual servers on them and use them as test beds for various reasons. I have created almost 100 VMs on their servers using vSphere clients and hence have loved the tool enormously. I hope to keep using it as long as i can. Its a great learning experience for me too.
  • It helps you manage your entire network, no matter how big or confusing it is.
  • Its user friendly and the GUI is pretty understandable
  • The changes that can be made after the VM has been created and cloning of the systems thats available makes the work quite easier and faster
  • Just that a better GUI will always be welcomed.
  • If there were some hard core tutorials you could have the link to attached with the help community, that would help too
  • Saved money on PC purchases by creating the VMs instead.
  • Lot of labor hours are saved by not having to image new PCs. Just create one Template VM and clone the others from that.
  • Ability to make sure VMs always turn back on once they are shutdown. This speeds up load times for users and is nothing like the normal desktop PCs which takes hours to come back up.
1) VMware
emulates virtual hardware and must account for all the underlying
system requirements— subsequently, virtual machine images are
significantly larger than containers. That said, it’s also possible to
run many discreet OS instances in parallel on a single host with VMware.
2) Unlike
VMware, Docker does not create an entire virtual operating system—
instead, all required components not already running on the host machine
are packaged up inside the container with the application. Since the
host kernel is shared amongst Docker containers, applications only ship
with what they need to run—no more, no less. This makes Docker
applications easier and more lightweight to deploy and faster to start
up than virtual machines.
3) Docker
containers are generally faster and less resource-intensive than
virtual machines, but full VMware virtualization still has its unique
core benefits—namely, security and isolation.
4) In short, for application/software portability, Docker is your safest bet. For
machine portability and greater isolation, go with VMware. \
And according to my needs and faster and safer option, VMware's vSphere is my choice.
1) vSphere is best in maintaining an entire lab of VMs or creating multiple VMs at once, if they all require the same configuration.
2) You can replicate some or all of the disks and the user selects destination location of disks, they don’t need to all go on the same destination datastore.
3) Replication is managed as a property of a VM and can be carried out on a per VM basis.

1) Only replicates powered-on VMs.
2)Fault Tolerant VMs, linked clones, and templates are currently not supported.
3)Automated fallback of VMs currently not supported using vSphere replication.

vSphere Feature Ratings

Virtual machine automated provisioning
Management console
Live virtual machine backup
Live virtual machine migration
Hypervisor-level security