Explore the key roadblocks to virtualizing mission-critical workloads. Discuss the potential benefits, in terms of performance and service-level delivery, in migrating these workloads to an internal cloud. Learn how PlateSpin solutions pave the way to migrating mission-critical workloads with little or no downtime, integrate non-disruptive testing in the virtual environment, and provide real-time workload protection and recovery.

1. Virtualizing Mission-critical
Workloads
The PlateSpin Story ®
Ari Glaizel
Product Manager
ari.glaizel@novell.com

2. Definitions

3. Workload: The (New) IT Paradigm
Application
Workload Middleware
Operating System
A workload is an A workload is A workload or a
integrated stack of portable and collection of
application, middleware, platform agnostic workloads makes
and operating system –it can run in up a business
that accomplishes a physical, virtual or service, which is
computing task cloud computing what the end user
environments consumes
3 © Novell, Inc. All rights reserved.

4. Another Term?!
Physical Server Virtual Host
1 workload per Multiple workloads per physical server
physical server
4 © Novell, Inc. All rights reserved.

5. Virtualization Market Drivers/Trends
Trends
Many companies have completed their first round of virtualization adoption
Virtualization users are moving beyond simple consolidation and dev/test
projects looking for other ways to leverage virtualization
Virtualization changes how capacity is, or needs to be, managed in
the datacenter
General need to reduce IT expenditure (CapEx and OpEx)
5 © Novell, Inc. All rights reserved.

6. PlateSpin Products Solve ®
Multiple Challenges
Cost Performance
Transformation is Each migration
takes too long
too expensive PlateSpin
Solutions
Risk
Test migrations to
ensure success
6 © Novell, Inc. All rights reserved.

7. Overview
PlateSpin Technology ®
Workload Profiling
• Agent-less data collection
• Resource sizing and analysis
Workload Portability
• Move, copy and replicate workloads
• Cross infrastructure boundaries
Workload Orchestration
• Policy based
• Proactive automation
7 © Novell, Inc. All rights reserved.

8. Evolution from Consolidation to
Workload Management
Active
Passive
Point in time
Continually and
Reclaim intelligently
resources and re-balance and
One time optimize optimize
consolidation environments resources
8 © Novell, Inc. All rights reserved.

9. Server Consolidation – Why ?
Server consolidation is the process of migrating
physical server workloads into a virtual environment.
Challenges – Before Solution – After
•Too many physical servers •Consolidated servers
•Underutilized servers •Available floor space
•Limited floor space •Optimized resource utilization
•High power/cooling •Reclaim unused resources
consumption •Green IT/reduced carbon footprint
•Low ROI and high TCO •High ROI and low TCO
9 © Novell, Inc. All rights reserved.

10. Mission Critical Workloads …
•
Are essential to maintaining and supporting
business operations
•
Minimal downtime tolerated during migration
•
Need to extend the benefits of virtualization (cost,
flexibility, efficiency, green) to all server workloads
•
Users are very performance sensitive when it comes
to running in virtual environments
Application owners must have peace-of-mind that
their workloads will run on a virtual machine
10 © Novell, Inc. All rights reserved.

11. PlateSpin Recon
®

12. PlateSpin Recon ®
1
Quickly identify
2
Right size resource
3
Reclaim unused
unused or bloated allocation based on resources for new
server resources real world usage applications and defer
new server purchases
Supply
Unused Server Resources
Demand
Virtual Machine
12 © Novell, Inc. All rights reserved.

13. Planning and Assessment
The assessment stage requires that administrators answer the
basic questions:
1. What are the resource requirements for these workloads?
2. What’s running in my workloads?
3. Are they suitable candidates for virtualization?
Once those initial questions are answered, we can proceed to the
planning stage via PlateSpin Recon. ®
PlateSpin Recon will help answer:
1. How will they fit into my virtual environment?
2. What is optimal workload placement for my
virtual environment?
13 © Novell, Inc. All rights reserved.

14. What is Recon?
Awareness and Planning
Data collection, analysis and reporting for the
What resources are
in the data center Data Center Manager and IT Architect
What workloads
are running on
those resources
How effectively are
workloads assigned
to resources
Targeted solutions to
solve specific
IT challenges Workloads Resources
14 © Novell, Inc. All rights reserved.

15. Consolidation Planning
What is It?
Planning the move from this (physical)… …to this (virtual)
15 © Novell, Inc. All rights reserved.

16. Consolidation Planning
How it works?
• Collect data (inventory or
performance) for consolidation
candidates (workloads)
• Create consolidation scenarios
to distribute workloads across
target servers
• Evaluate scenarios based on
TCO, space, power, utilization
and consolidation
• Maximize utilization and adjust
resource allocation to meet
consolidation goals
16 © Novell, Inc. All rights reserved.

17. Consolidation Planning
One-time vs. Continuous
• One-time • Continuous
• Aggressive • Conservative
• Try to virtualize as much as • Multiple rounds of virtualization,
possible at once select “lowest hanging fruit”
• Goal – maximum cost saving • Goal – successful technology
• One-time project adoption (IT and end-users)
• Low upfront cost
• Persistent software
(sometimes free) (plan when you walk with
the latest information)
• Risks
• Software has a cost
– Hardware can’t support the
number of servers virtualized
– Hardware can’t support the
type of workloads virtualized
17 © Novell, Inc. All rights reserved.

18. How Virtualization Changes
Requests for Resources
I need 3
servers to run
this application.
Before Virtualization After Virtualization
18 © Novell, Inc. All rights reserved.

19. How Virtualization Changes
Hardware Purchases
Before Virtualization After Virtualization
$20k - purchased to meet the $200k - purchased to meet the
needs of a user needs of all users
19 © Novell, Inc. All rights reserved.

20. What is Virtualization Capacity
Management?
Awareness of
Available Resources
Identification Virtualization Opportunities
of Bottlenecks Capacity for Reclamation
Management
Configuration Issues
Cost Saving/Avoidance
20 © Novell, Inc. All rights reserved.

21. Virtualization Capacity Management
Awareness of Available Resources
What we want What we have
21 © Novell, Inc. All rights reserved.

22. How to Successfully Manage Capacity
• What administrators need to know:
– Who is using your VMs?
– What are they using your VMs for?
– When will they be done with your VMs?
– Where are your VMs assigned to run?
– Why don’t you know everything about your VMs?
• Develop standard VMs configurations, and identify
VMs that don’t conform
• Charge users for their usage of the virtualization
environment, at a minimum track who is using how
much of your environment
22 © Novell, Inc. All rights reserved.

23. Demo
Use PlateSpin Recon to analyze a 'critical
®
SUSE 11 Server' workload to determine if
®
it is a candidate for virtualization.
23 © Novell, Inc. All rights reserved.

24. PlateSpin Migrate
®

25. PlateSpin Migrate ®
Data
Applications
Operating System
Physical Servers Server Workloads Virtual Host
1
Migrate Windows and Linux
2
Test new workload to
3
Sync over changes that
workloads into a VMware, ensure it runs as occurred during the test
Microsoft Hyper-V or Xen predicted with no impact cycle and put new
virtual environment to production server workload live
25 © Novell, Inc. All rights reserved.

26. Virtualization Steps
1
Initial
Workload
Copy
App. Users
2
Test
and
Verify App. Test
App. Users Team
3 Server
Sync
26
4 Cutover
© Novell, Inc. All rights reserved.
App. Users

27. Initial Migration
In the initial migration, we will perform a one-time P2V
migration of the workload to a dedicated test environment. In
this process we can make modifications to the workload in
terms of IP, disk size, hostname, etc. These changes help
ensure that the workload can be successfully started without
any disruption to the production environment.
The VM will be used to:
1. Perform acceptance testing
2. Validate the results obtained during the assessment and
planning stage
3. Minimize cutover outage if an offline cutover is needed
27 © Novell, Inc. All rights reserved.

28. Staged Transfer With Images
• Site to site
interconnect
• Large Bandwidth
• Small Used Disk
Space (<50 GB)
Requirements
1
Source Site Target Site
28 © Novell, Inc. All rights reserved.

29. Direct Transfer
(Peer-to-peer)
• Site to site
interconnect
• Large Bandwidth
• Small Used Disk
Space (<50 GB)
Requirements
2 3
1
Classic File Transfer
SAN Replication
Removable Media
Source Site Target Site
29 © Novell, Inc. All rights reserved.

30. Staged Transfer With Images
and Server Sync
• Site to site
interconnect
• Large Bandwidth
• Small Used Disk
Space (<50 GB)
Requirements
2 3
1
Classic File Transfer
SAN Replication
Removable Media
Source Site Target Site
4
30 © Novell, Inc. All rights reserved.

31. Testing and Validation
Testing and validation is an important step in the critical
workload migration process. It allows users to reduce
the risks involved with migrating workloads into a virtual
environment. The ability to test the workload before
performing a cut-over is a pro-active approach
allows us to:
• Identify and address any potential performance issues
• Identify and address any compatibility issues
• Test different workload configurations to optimize
performance in the virtual environment
31 © Novell, Inc. All rights reserved.

32. Server Sync: Optimized Testing
Test your virtualized environment with minimal downtime
Without PlateSpin ®
Migrate
Test
Cut Over
With PlateSpin
Migrate
Test & Validate
Cut Over
32 © Novell, Inc. All rights reserved.

33. Final Cutover
As a result of the of the testing and validation stages, the source
and target workloads will no longer be in sync, as data may have
changed on the source workload. The workloads need to be
synchronized before the final cutover can be performed. The
PlateSpin Server Sync functionality allows users to sync the source
®
and target and perform the cutover in one single operation.
This allows us to :
• Minimize the outage window
• Reduce service interruption
• Maintain data consistency.
• Limit the replication to the changes without the need to replicate
the entire workload
33 © Novell, Inc. All rights reserved.

34. Automation and Platform Heterogeneity
Reduce the manual effort and logistics involved in
implementing a site consolidation
Automate the planning and migration/relocation of
hundreds of physical servers and virtual machines
Migrate Windows and Linux servers and VMware,
Microsoft Hyper-V and Xen virtual machines
Mitigate the risk by testing workloads in their
new location
Broadest platform and hyper-visor support in industry,
supports the most complex IT environment
34 © Novell, Inc. All rights reserved.

35. Auditing and Change Control
Track workload migration history as the workloads
move around the datacenter.
Quickly summarize changes to a workload to expedite
change control process and be able to answer “what
has changed?”
Review migration configurations to understand VMware,
Microsoft Hyper-V and Xen virtual machines
Mitigate the risk by testing workloads in their new location
Only migration tool on the market that provides
complete logging of the entire process
35 © Novell, Inc. All rights reserved.

36. Cost Savings
Scheduling functionality helps minimize costs for
staffing during off-hours
E-mail notifications removes the tether during the
migration process – no need to sit and watch the
progress bar
Optimized File-transfer reduces the duration
of migrations
Simplified testing reduces downtime for your workloads
reducing costs associated with a server outage
Reduces overall costs of all types of migration projects
36 © Novell, Inc. All rights reserved.

37. Demo
Based on previous consolidation assessment, set up
migration as well, show how you would set up a server
sync once 'testing' is complete.
37 © Novell, Inc. All rights reserved.

38. Consolidated Disaster Recovery –
P2V DR via PlateSpin Protect
®

39. Leveraging Virtual Infrastructure to
Protect Physical Servers
Physical Production Servers
Virtual Recovery Hosts
Physical Production Servers
39 © Novell, Inc. All rights reserved.

40. PlateSpin Protect and Forge ®
Users
1
Replicate servers
(physical or virtual)
into a secondary
virtual environment
Production Server Secondary Environment
Users
2
IT admin tests
workloads in new
environment to
ensure they run
as expected
Production Server Secondary Environment
Production server
3
goes down, power
up virtual machines
in secondary
environment in
Production Server
Secondary Environment minutes
(Offline)
40 © Novell, Inc. All rights reserved.

41. PlateSpin Protect ®
Users
1
Replicate servers
(physical or virtual)
into an image library
Production Server Image library
Users
2
Replicate incremental
changes on a daily,
weekly or monthly basis
Production Server Image library
3
Production server goes
down, deploy image to
new or existing hardware
over the network
Recovery Server Image library
41 © Novell, Inc. All rights reserved.

42. Consolidated Disaster Recovery
Benefits
• Software that replicates whole workloads into local
or remote consolidated environment
• Create protection plans that can replicate changes to
production server on hourly, daily or weekly basis
• Testing recovery plans provides peace of mind
knowing workloads will run in the event of downtime
• In the event of downtime users are switched and can
run off secondary workload
• Point in time recovery allow you to roll back to the last
known good state of a protected workload
42 © Novell, Inc. All rights reserved.

43. Consolidated Disaster Recovery
How Does It Work?
Step 1:
Replicate servers
(physical or virtual) into a
secondary consolidated
Production Server Secondary Environment virtual environment
Step 2:
Test workload in new
environment to ensure it
runs as predicted
Production Server Secondary Environment
Step 3:
Production server goes down, the
workload can run in a virtual
environment until new hardware is
provisioned, thus reducing downtime
Secondary Environment
Step 4:
Restore/recover workload to new
or existing hardware in minutes
Recovery Server Secondary Environment
43 © Novell, Inc. All rights reserved.

44. Where Do We Fit?
Solution Cost RPO RTO TTO
Near Zero
Server Clustering $$$$$$ Near Zero Near Zero (Impacts
production data)
PlateSpin Minutes
Consolidated $$$$ Minutes Minutes (No impact to
Recovery production data)
Hours (Requires
Image Capture $$$ 24h Hours additional
hardware)
Tape/Manual Days
$ 24h+ Days
Rebuild (Not practical)
44 © Novell, Inc. All rights reserved.

45. How Novell Delivers Intelligent ®
Workload Management
Build Secure Manage Measure
SUSE Linux
® Novell Identity PlateSpin ® Novell Business Service
Enterprise Server Manager Orchestrate Manager
SUSE Studio Novell Access Novell ZENworks Novell Business Service
Manager Configuration Level Manager ™
SUSE Linux Management
Enterprise JeOS Novell Roles Based Novell Business
Provisioning Module PlateSpin Migrate Experience Manager ™
Novell ZENworks
® ®
Configuration Novell Access PlateSpin Recon Novell myCMDB ™
Management Governance Suite
PlateSpin Protect Novell Sentinel ™
SUSE Appliance Novell Privileged
Toolkit User Manager PlateSpin “Atlantic” Novell Sentinel Log
Manager
Novell Workshop Novell SecureLogin ®
PlateSpin “BlueStar”
Novell Compliance
Novell Cloud Novell Definitive Automation Solution
Security Service Software Library
* Covered in VWM 100
* Available by end of 2010
45 © Novell, Inc. All rights reserved.

46. Questions...

48. Unpublished Work of Novell, Inc. All Rights Reserved.
This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc.
Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope
of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified,
translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc.
Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.
General Disclaimer
This document is not to be construed as a promise by any participating company to develop, deliver, or market a
product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in
making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents
of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any
particular purpose. The development, release, and timing of features or functionality described for Novell products
remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to
make changes to its content, at any time, without obligation to notify any person or entity of such revisions or
changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc.
in the United States and other countries. All third-party trademarks are the property of their respective owners.