
COMPARISON GUIDE
COMPARISON GUIDE / 11
VMware vSphere 6 with Operations Management
Key Features and Benefits Comparison
4. Availability and Business Continuity
KEY FEATURES AND BENEFITS VMWARE VSPHERE®
WITH OPERATIONS
MANAGEMENT™ 6
MICROSOFT WINDOWS SERVER
2012 R2 HYPER-V & SYSTEM CENTER
2012 R2
RED HAT ENTERPRISE
VIRTUALIZATION 3.5
High Availability – Minimize downtime resulting from server and operating system failures
• Simple HA Configuration - Availability solutions tied to operating systems or applications require complex setup
and configuration. In contrast, configure HA with a single click from within vCenter.
3
No, Microsoft implements HA through Setup
of Windows Failover Clustering. Enabled
per-VM
No, requires the setup of power management
for each host and manual per-VM
configurations for HA with no top level tool
or visibility into configuration of the status of
individual VM’s HA
• No Single Point of Failure or External Dependencies - VMware vSphere HA ensures virtual machines restart even
if vCenter Server is unavailable, without a dependency on DNS
3
Yes, but requires cluster members to be
members of an active directory domain
No, VMs won’t restart if RHEV Manager is
down
• Resource Checks - Ensure that capacity is always available in order to restart all virtual machines aected by server
failure. HA continuously monitors capacity utilization and “reserves” spare capacity to be able to restart virtual
machines.
3
Limited, cluster reserve state will suggest
placement not occur, but won’t prevent
administrators from manually overriding a
placement recommendation
No
• VM Restart Priority - Ensure the most critical virtual machines are restarted first by setting virtual machine restart
priorities. Easily select multiple virtual machines to establish resources priorities for an entire cluster.
3
Requires per-VM configuration. Implementing
high priority restart policy can impact
availability of VMs with default restart policy,
putting them into save state if enough
resources aren’t available in the cluster
Must be configured at the virtual machine
level for each and every VM. It is not possible
to order the startup order of the virtual
machines and provide granular recovery
options, you can only set VMs individually to
Low, Medium, or High
• VM Component Protection – Protect virtual machines against storage failures where permanent device loss occurs
or all paths are down for block (FC,iSCSI,FCoE) and file (NFS) storage
3
No configurable parameters or capabilities
exist to protect against permanent device
loss or issues where all paths are down
No configurable parameters or capabilities
exist to protect against permanent device
loss or issues where all paths are down
• VMware HA Health Check and Cluster Operational Status - View a dashboard in the vSphere Web Client that
displays the current VMware HA operational status, including the specific status and errors for each host in the
VMware HA cluster
3
Limited, requires Windows Failover
Clustering for full operational status
Very limited, RHEV-M provides no insight into
HA in a dashboard or granular views into
individual VM settings without drilling down
into each and every virtual machine
• Multi-Processor Fault Tolerance (FT) - Provide zero downtime, zero data loss continuous availability against
physical server failures through a seamless stateful failover. Single click configuration, with automatic secondary
virtual machine creation in the event of a failure, ensuring continuous protection. Fault tolerance is oered without
any dependency on the guest operating system.
3
No No
Comentarios a estos manuales