DRAGAN JELČIĆ

Meridijana IT
 Introduction
 Server infrastructure
 Comparing Hyper-V and ESX
Server
 Comparing Microsoft System
Center and VMware vSphere
 Questions
1. Requests to IT departments
- Increase the efficiency of installed hardware
- Increase the availability
- Increase scalability
- Increase security
- Reduce administration
- Reduce costs
- One server - one application
- Test environment that matches production
- Support for older (legacy) business application
- Reduce energy costs
-…
- How???
1. Migration of old applications on new
hardware
2. Consolidation of server resources
3. “Rapid Deployment” and Migration
4. Increase system security
5. Building a test environment
6. Emergency Disaster Recovery
7. …
1. The rules for building a “good” information
system ...
- Avoid any “single point of failure”
- Size system under the peak load
- Ensure regular backup
- Ensure scalability
-…
2. Popularly said, all must be "double"
1. Is it SAN a good solution?
2. Everything that is written in the advertising
materials on the SAN-in is true, but ...
3. Storage is usually the “single point of failure”
4. SAN performance is lower than the local disks
5. It is much more expensive than local drives
1. Are blade servers a good solution?
2. Everything that is written in the advertising
materials about them is true, but ...
3. Blade Chassis is the "single point of failure“
4. Switches (Ethernet i FC) are the bottleneck
5. Limited expandability with type and number
of devices
6. Extremely complicated and expensive
cooling
1. Microsoft
- Hyper-V Role Part of Windows Server 2008 R2
- Hyper-V Server 2008 R2 Free

2. VMware
- ESX Server 4.0 of Part of vSphere
- ESX xi Free
 Microkernel Hypervisor
Monolithic Hypervisor simple partitioning
simpler than those of modern increased reliability
kernel, but still complex
does not contain foreign code
contains its own driver model
All drivers are running within the
VM's
VM 1 VM 1
VM 2 VM 3
(“Admin”) (“Parent”)

Virt. VM 2 VM 3
Layer (“Child”) (“Child”)

Hypervisor

Hypervisor

Hardware Hardware

Microkernel Hypervisor have secure architecture with minimal attack surface

1. Windows Server 2008 –Hyper-V Role
2. Hyper-V Server 2008 (Free)
3. Features-at-a-glance
- 4-way Virtual SMP
- Up to 64GB RAM per VM
- Live Migration & Quick Migration
• Windows Server 2008 R2 Failover Clustering
- Live backups using Volume Shadow Copy
Service
- Direct SAN LUN mapping
- Offline VHD tools
- No USB in guests
1. Leader in the enterprise virtualization
products
- 78% of the market (IDC Oct 16th, 2008)
2. Features-at-glance
- 8-way virtual SMP (Enterprise Plus)
• 4-way virtual SMP for the other editions
- Up to 255 GB RAM per VM
- Support for a wide array of both Windows and
Linux VMs
- VMotion
- Direct SAN LUN mapping, boot from SAN
- No USB is Guests
 ESXi ESX 4
◦ Free ◦ Part of vSphere
◦ No Service Console ◦ Linux based Service
◦ 32 MB Console
◦ Managed by vSphere  Run scripts
Client  Load drivers and third
party products
◦ Can use vMotion, ◦ 800 MB
DRS, HA, FT (when
used with vSphere) ◦ Managed by vSphere
Client
◦ Can use vMotion,
DRS, HA, FT

Detailed comparison at:

http://kb.vmware.com/selfservice/microsites/search.do?language=
en_US&cmd=displayKC&externalId=1006543
Test Environment
(Oct. 2008 -Hyper-V RTM & ESX 3.5)
- HP ProLiantML370 G4
• 2 Intel quad-core Xeon processors running at
1.86GHz
• 8GB of RAM
• 8 -72GB 15,000rpm
- 8 Active VMs running WS2008 Enterprise x64
• 6 –File servers reading and writing130 MB of files
from 18 clients
• 2 –SQL Server 2005 running 27 queries from 6
clients
• Test suite run three times and averaged
Test Environment
(May 2008 -Hyper-V & ESX 3.5)
- HP ProLiantML370 G4
• 2 Intel quad-core Xeon processors running at 1.86GHz
• 8GB of RAM
• 8 -72GB 15,000rpm
- 4 Active VMs running
- WS2008 Enterprise x64 & SQL Server 2005 EE
- 4 clients –10 connections per client
- Running 27 queries -80% read 20% update
- Test suite run three times and averaged
 1. CaseLab Euler3D BENCHMARK Version 2.2
7

W2K8R2e
4
I55xx 2,6

W2K8R2h
3
vmEsx4

vmH-V2
2

0
1 2 3 4 5 6 7 8
ESX Server Hyper-V

•No reliance on •Less expensive

Windows •Broader hardware
•Broader guest support support
•The best performance •Very good performance
•Bigger hypervisor / •Smaller hypervisor /
smaller platform bigger platform
•Better scalability for •Cost effective for
larger businesses smaller business
Features at a glance
1. Live Migration & Quick Migration
- Live Migration requires WS2008 R2 or Hyper-V Server
2008 R2
2. Intelligent placement
- Virtual Machine Manager
3. Heterogeneous VM management
- VMM & vCenterServer
4. Dynamic resource management
- VMM PRO
5. Deep end-to-end management
- Operations manager
6. OS & application deployment and patching
- Configuration Manager
Features at a glance
1. VMotion
- Addresses planned downtime
2. High Availability (HA) and Fault Tolerance
(FT)
- Address unplanned downtime
3. Distributed Resource Scheduler (DRS)
- Dynamic resource management
4. Distributed Network Switch
- Dynamic network parameters
VMware Microsoft
 vMotion  Live Migration
◦ Moves VM between ◦ Moves VM between
servers nodes
◦ No downtime ◦ No downtime
◦ Requires vCenter Server ◦ Requires WS08R2
(Virtual Center Server) Failover Clustering
◦ SAN Infrastructure ◦ SAN Infrastructure
◦ GB Ethernet ◦ GB Ethernet
 Quick Migration
◦ Moves VHD files
between nodes
◦ Brief downtime
◦ Requires WS2008
Failover Clustering

•Need to be aware of processor compatibility

VMware
 High Availability
◦ Automatic restart
 Restarts VMs
◦ Some downtime
◦ Host and guest level
◦ Optimizes VM
placement using DRS
◦ Up to 32 nodes per
cluster
 Fault Tolerance (new)
◦ No downtime
◦ Lock Step VMs -
vLockstep
◦ Limited to a single vCPU
Microsoft
 Failover Clustering
◦ Automatic Failover
 Resumes services
◦ Minimal downtime
◦ Host and guest level
◦ Up 16 nodes per
cluster
◦ Microsoft servers are
cluster aware
 Windows Server
 Exchange
 SQL Server
 SharePoint
VMware Microsoft
 DRS (Distributed  VMM PRO (Performance
Resource Scheduling) Resource Optimization)
◦ Can automatically move ◦ Can automatically move
VMs between hosts in VMs between hosts in
response to workload response to workload
(VMotion) (Live Migration)
◦ More Advanced features ◦ Can automatically alert
 Global scheduler or execute scripts based
 Dynamically workload on resource utilization
across resource pools ◦ Requires Operations
 vAPP–Manage VMs as a Manager
group
 Distributed Power
Management
◦ Requires vCenterServer
VMware
 VMware Consolidated
Backup (VCB)
◦ Full and incremental VM
file backups
◦ Reduced server load
through backup proxy
server
◦ Recover whole VMs
◦ Recover individual files
and folders from
Windows VMs
Microsoft
 Windows Server
Backup
◦ Very basic
◦ Uses VSS for snapshots
◦ Restore and backup
only at the volume level
 Data Protection
Manager
◦ Backs up and restores
Windows Server,
Hyper-V, SQL Server,
Exchange SharePoint
◦ VSS based
◦ DPM to DPM replication
for offsite protection
1. Heterogeneous Management
- VMM 2008 R2
- Manages Hyper-V, Virtual Server 2008 and ESX Server via
vCenterServer
- Support almost all VMware management functions
include VMotion
2. Deep application monitoring and management
- Operations Manager
• Hyper-V, Exchange, SQL Server others via Mgmt Packs
3. Application level backup and restore
- Data Protection Manager
• Exchange, SQL Server, SharePoint
4. Software deployment
- Configuration Manager
• Server and client OS deployment
5. Add and remove VHD to a running VM
1. Broad Linux VM support
2. Memory Over Commitment
- Shared memory pages between VMs
3. NIC Teaming
- Aggregate multiple NICs together
4. Distributed Power Management
- Transfer load off lightly used hosts and shut them
down
5. Distributed Network Switch
- Enables shared network configuration between
servers
6. Storage VMotion
- Enables moving virtual machine files from one
storage array to another without affecting the
operation of that Virtual Machine
1. To take full advantage of all features except
the VMware Infrastructure and ESX server we
need
- Windows Server for Virtual Center
- Windows computer for Virtual Center Client
- Windows Server for VMware Consolidated Backup
- Microsoft AD for complete comfort
2. Why, except Windows Server add something
else in the environment?
1. VMvare have not the opportunity to use
same physical server for a services and for
virtualization
2. Microsoft offers the possibility that we
utilize unused resources on the “big”
servers used for virtualization for less
demanding servers and services
3. On the Microsoft solution the same
administrative tools is to used for managing
physical and virtual infrastructure
VMware Microsoft
•Operating System •Operating System
–Windows Server 2008 –Windows Server 2008
Datacenter $2381 x 20 Datacenter $2381 x 20
= $47620
= $47620
•Virtualization Platform
•Virtualization Platform –Hyper-V included w/WS08
–ESX Server 4 included w/ •Management Platform
vSphere 4
–System Center
•Management Platform Management Suite
–vSphere 4 E+ $4360 x 10 Datacenter $1482 x 10
= $43600 = $14820
–vCenter Server $4995
•Total $96,215 •Total $62,440
VMware ESX + VC Microsoft Hyper-V + SCVMM

 Longer on the market  Works on any Windows certified

hardware

 Better memory management  Yu own Hyper-V, why not use it?

 Support for more OS  Better technical support

 VMotion  Same administrative tools for whole IS

 Storage VMotion  Possibility to combine on the same

physical server

 Microsoft solution for the same system performance with

mostly Windows servers is about 2 times less expensive
dj@meridijana.hr