Transcript Pricing Committee Template

Virtual Excellence Q1 2009
Product and Solutions Update
Libor Nedas
[email protected]
AGENDA
New VI names
Severity 1 SR
Converter 4.0
VC Heartbeat
VC server for LINUX
Open Source VMFS driver
Partner DEMO Center
MVP with DEMO
NEW VI Names
VMware vCenter
VMW VDI -> VMW View
VMW Virtual Center ->VMW vCenter
Server
VDM -> VMW View Manager
VMW LCM -> VMW vCenter LCM
VMW SRM -> VMW vCenter SRM
VMW Lab Manager -> VMW vCenter LM
VMW Stage Manager -> VMW vCenter SM
VMW Converter -> VMW vCenter
Converter
VMW Update manager -> VMW vCenter
UM
VMFS -> VMW vStorage VMFS
VDM WEB access -> VMW View portal
Severity 1 SR
New Requirement for Opening Severity 1 Support Requests
VMware Global Support Services is committed to addressing
critical support issues. In order to ensure critical issues are
being handled as effectively as possible, we are changing
the process for submitting Severity 1 support requests.
Beginning on February 21, all Severity 1 support requests
must be opened by calling technical support. This will
enable us to provide personalized, real-time support during
critical situations. Customers with Web-only support
programs, such as Silver Support and Subscription, Fusion
Per Incident Support, Complimentary Support and SDK will
be able to open severity 2, 3 and 4 support issues through
the Web.
vCenter Converter 4.0
Physical to virtual machine conversion support for Linux (RHEL,
SUSE and Ubuntu) as source
Physical to virtual machine conversion support for Windows Server
2008 as source
Hot cloning improvements to clone any incremental changes to
physical machine during the P2V conversion process
Support for converting new third-party image formats including
Parallels Desktop virtual machines, newer versions of Symantec,
Acronis, and StorageCraft
Workflow automation enhancements to include automatic source
shutdown, automatic start-up of the destination virtual machine
as well as shutting down one or more services at the source and
starting up selected services at the destination
Target disk selection and the ability to specify how the volumes are
laid out in the new destination virtual machine
Destination virtual machine configuration, including CPU, memory,
and disk controller type
vCenter Converter 4.0
The following features are no longer supported:
NT4 hot cloning
ESX 2.5 destination
vCenter Converter 4.0
You can install all components of VMware vCenter Converter
Standalone 4.0 (Converter Standalone client, Converter
Standalone server, and Converter Standalone agent) on the
following platforms:
Windows 2000 SP4
Windows XP Professional (32 bit and 64 bit)
Windows 2003 (32 bit and 64 bit)
Windows Vista (32 and 64 bit)
Windows Server 2008 (32 bit and 64 bit)
Red Hat Enterprise Linux 4.0 (32 bit and 64 bit)
Red Hat Enterprise Linux 5.0 (32 bit and 64 bit)
SUSE Linux Enterprise Server 10 (32 bit and 64 bit)
Ubuntu 6.x
Ubuntu 7.x (32 bit and 64 bit)
vCenter Converter 4.0
You can install Converter Standalone 4.0 server and
agent (no GUI client supported) on the following
platforms:
Red Hat Enterprise Linux 3.0
SUSE Linux Enterprise Server 8
SUSE Linux Enterprise Server 9 (32 bit)
Ubuntu 5.x
vCenter Converter 4.0 - Import
Converter Standalone 4.0 can convert and reconfigure any local or remote physical
machine running an operating system noted in Supported Guest Operating
Systems.
Workstation 6.5.x, Workstation 6.0.x, Workstation 5.x, and Workstation 4.x1
VMware Fusion 1.x, 2.x
ESX Server 3.x
ESX Server 3i version 3.5 Installable and ESX Server 3i version 3.5 Embedded
ESX Server 2.5.x (if VirtualCenter 2.x manages ESX Server)
VMware Server 1.x, 2.x
VirtualCenter 2.x
Microsoft Virtual PC 2004 (for Windows only), Microsoft Virtual PC 2007 (for
windows only)
Microsoft Virtual Server 2005, and 2005 R2
VMware Consolidated Backup
Acronis True Image Echo 9.1, 9.5, and Acronis True Image 10, 11 (Home
product)1
Symantec Backup Exec system Recovery (formerly LiveState Recovery) 6.5,
7.0, and 8.0, LiveState Recovery 3.0 and 6.0
Norton Ghost version 9.0, 10.0, 11.0, 12.0, 13.0, and 14.0 (.sv2i files)
Parallels Desktop for Microsoft Windows and Mac OS x 2.5, 3.0
StorageCraft ShadowProtect 2.0, 2.5, 3.0, 3.1, and 3.22
OVF spec version 0.93
Local OVF or OVA file3
URL to and OVF or OVA file3
vCenter Converter 4.0 - Export
VMware Workstation 6.5.x, 6.0.x, and 5.x 2
VMware Player 1.x, 2.0.x, and 2.5.x
VMware Server 1.x and 2.x
Vmware Fusion 1.x and 2.x
ESX 3.x
ESXi 3.5 Installable and ESXi 3.5 Embedded
VirtualCenter 2.x
OVF and OVA virtual appliances3
vCenter Converter 4.0
The support for the following features is experimental
in Converter Standalone 4.0:
Conversion of virtual machine sources that run
Windows by using Converter Standalone server for
Linux
Conversion of source machines running Ubuntu 8.x
operating systems.
vCenter Converter 4.0
vCenter Converter Standalone
vCenter Converter Integrated
Feature rich free product for P2V, V2V
Enterprise-class product for managing
and automating large scale P2V and
migration
P2V and V2V migration projects
Linux P2V support is available for Standalone
version only
V2Vconversions
Large scale server consolidation projects
using VMware Infrastructure 3
Centrally schedule and manage periodic
conversion tasks
Scheduled Conversions
Recurring Conversions
CLI
vCenter Server Integration
Cold Cloning (Using a BootCD)
LINUX P2V
Supported Conversions
– Source: powered-on machine (hot clone only)
– Destination: managed destination only (vCenter/ESX/ESXi only)
Requirements and Limitations
– Remote SSH to source machine enabled
– Root or sudo login
– Volume-based file-level copy only
– GRUB only, no LILO
– File system types preserved: ext2, ext3, reiserfs, vfat (all else 􀃆
ext3)
– LVM volumes can be read, but are not preserved in new VM
– If multi-boot system, only the current system is converted
P2V Motion for Windows P2V
Synchronize Changes
– Keeps track of changes after snapshot and applies changes in a
post-clone
synchronize step – minimizes lost transactions during hot clone
– Option to coordinate source shutdown and destination power-on
– Works in conjunction with Windows services
Requirements and Limitations
– Available only for live conversions of Windows XP and higher
– Volume-based block-level cloning only (no resizing of volumes)
VirtualCenter 2.5 U4
Guest Operating System Customization Improvements VirtualCenter now supports customization of
Windows Server 2008 guest operating systems.
Performance Overview Charts - VirtualCenter 2.5 Update
4 introduces the Performance Overview plug-in,
which provides a single view of key performance
metrics for CPU, memory, disk, and network without
having to navigate through multiple charts. The
aggregated charts show high-level summaries of
resource distribution.
To install the Performance Overview plug-in, see
Installing the Performance Overview Plug-In in
VirtualCenter 2.5 Update4 (KB 1008296)
VirtualCenter Availability Overview
High availability for VC is growing in importance
VC is now critical for customers running VMware in production

Current architecture has several potential points of failure
HA protects VC running in a VM against hardware/OS failures, but…

Lacks application awareness, WAN failover capability

~60% of customers run VC on a physical server
VC Federation won’t address this for 2+ years
Competitive solutions are expensive, complex and lack support for
database, WAN failover


Alternative solutions cost $8K and up for limited capability
vCSHB offers a compelling VC Availability solution
Proven technology supports SQL, Exchange, Blackberry availability
Provides rapid VC app and database failover on LAN or WAN
Spectrum of VC Availability Options
Filling the VC Availability & geographic failover gap prior to Federated
VC is a key opportunity for revenue generation & competitive
differentiation vs. MSFT System Center VMM
MSCS
Clustering
VC / DB with
VMware HA
Database
Clustering
• (+) Protects
data
• (-) No VC
monitoring
• (+) Protects
hardware
• (-) Does not
protect against
application
failures
• (-) Only covers
virtual instances
• (+) Protects
against more
kinds of failures
• (-) Added
licensing costs
• (-) Complex to
setup and
maintain
Fully
Federated
VC (2010+)
• (+) Protects
against all
kinds of
failures
• (+) Multiple VC
instances in an
environment
for redundancy
& failover
• (+) Resiliency
model similar
to Active
Directory
Product Proposal: VirtualCenter Heartbeat
3rd party OEM , rebranded & re-sold by VMware to protect the VC Server AND its
Database in any type of configuration (LAN, WAN, P2V, V2V)
VirtualCenter Protection
VCMS app monitoring, data replication,
performance monitoring through VI
SDK integrations
VirtualCenter 2.5.0+
Database protection
SQL module with SQL app monitoring, data
replication, and performance monitoring
SQL Server 2005+
VirtualCenter Heartbeat: Installation & Management
ACTIVE
PASSIVE
PASSIVE
ACTIVE
SWITCHBACK
FAILOVER
DISASTER
STEP
Step2:4
1:
3
Heartbeat
RECOVERY
Install
Configure
VCMS
Clone
VCMS
VCMS
module
Fix
failure,
module
Move
primary
runs
and Heartbeat
on will
and
Heartbeat
re-synchronize
secondary
primary
module
andto
detect
failure,
primary
module
on
and
offsite location
instances
secondary
to
switch back
automate
existing
VCMS
for
communicate
instances
(VMware
full DR
failover, resupport
Converter for
connect hosts
P2V config,
(minimizing
NTBackup for
service
P2P config)
disruption)
vCSHB
channel
PRIMARY
SECONDARY
Comparison of Host Based Replication Solutions
Doubletake
Steeleye
XOSoft (CA)
VCenter
Server Heart
Beat
Hardware Failure Protection
Yes
Yes
Yes
Yes
SQL Protection Module
Yes
Yes
Yes
Yes
Application Awareness
Low
Medium
Medium
High
VirtualCenter –specific module
No
Yes
No
Yes
Cost (for SQL modules today)
$6-8K
$6-8K
$8-10K
$10-12K
Current Features &
Functionality
Comparison : VirtualCenter Availability Alternatives
VMware HA
Windows
Clustering
Windows Hostbased
Replication
X
Yes
Yes
VC Server OS
Yes*
Yes
Yes
VC Server hardware
Yes*
Yes
Yes
X
Yes
Yes
Database OS
Yes*
Yes
Yes
Database hardware
Yes*
Yes
Yes
Network Connectivity
x
Yes
Yes
Complexity of setup
L
H
M
Cost
L
H
M
Failure type / Protection type
VC Server application components
Database application components
* - Virtual Instances only
vCenter Server for LINUX
It’s written natively in C++ - no Windows environment emulation is in place !
It’s virtual appliance running CentOS 5 inside (recompiled RHEL5 stripped down of
RedHat logos and trademarks)
There’s no embedded database for now, but will be in GA version – currently it
supports only Oracle, but GA version will support Oracle, DB2 and one of
MySQL or PostgreSQL (yes, there will be free option !)
VI Client for Linux is not part of this project and will not be delivered together with
GA of vCenter for Linux – VMware is now looking for options like unified client
based on Adobe Flex for all platforms – accessible through web interface..
Linux based vCenter will not support Guided Consolidation (incl. Converter),
guests customizations..
All interfaces of vCenter remains the same – ie. VI perl toolkit will works in the
same way for both platforms..
Add-on products like SRM will be delivered as virtual appliances based on Linux
later on
http://communities.vmware.com/community/beta/vcserver_linux
Open Source VMFS driver
This driver enables read-only access to files and folders on partitions
formatted with the Virtual Machine File System (VMFS). VMFS is a
clustered file system that is used by the VMware ESX hosts to
store virtual machines and virtual disk files.
The VMFS driver is developed and maintained by fluid Operations
and is included in upcoming releases of the eCloudManager
product, where it is used to allow enhanced features like
offloaded backups of virtual machines hosted on VMware ESX
hosts.
The VMFS driver comes with a command line interface (CLI) to mount
and analyze VMFS volumes. The VMFS driver was tested on Linux
and Windows based hosts, but should work on any platform that
supports Java.
http://code.google.com/p/vmfs/
Partner DEMO Center
MVP in Action