Virtualizing Mission-critical Workloads: The PlateSpin Story

Virtualizing Mission-critical WorkloadsThe PlateSpin® Story

Ari GlaizelProduct [email protected]

Definitions

© Novell, Inc. All rights reserved.3

Workload

Application

Middleware

Operating System

Workload: The (New) IT Paradigm

A workload is an integrated stack of application, middleware, and operating system that accomplishes a computing task

A workload is portable and platform agnostic–it can run in physical, virtual or cloud computing environments

A workload or a collection of workloads makes up a business service, which is what the end user consumes


Another Term?!

Physical Server Virtual Host

1 workload per physical server

Multiple workloads per physical server


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)


PlateSpin® Products Solve Multiple Challenges

Cost Performance

Risk

PlateSpinSolutions

Each migration takes too long

Test migrations to ensure success

Transformation is too expensive


OverviewPlateSpin® 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


Continually and intelligently re-balance and optimize resources

Reclaim resources and optimize environments

One time consolidation

Evolution from Consolidation to Workload Management

Point in time

PassiveActive


Server Consolidation – Why ?

Server consolidation is the process of migrating physical server workloads into a virtual environment.

Challenges – Before•Too many physical servers•Underutilized servers•Limited floor space•High power/cooling consumption•Low ROI and high TCO

Solution – After•Consolidated servers•Available floor space•Optimized resource utilization•Reclaim unused resources•Green IT/reduced carbon footprint•High ROI and low TCO


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

PlateSpin® Recon


PlateSpin® Recon

Supply

Demand

Unused Server Resources

Quickly identify unused or bloated server resources

Right size resource allocation based on real world usage

Reclaim unused resources for new applications and defer new server purchases

Virtual Machine

1 2 3


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?


What is Recon?Awareness and Planning

Data collection, analysis and reporting for the Data Center Manager and IT Architect

What resources arein the data center

What workloads are running on those resources

How effectively are workloads assigned

to resources

Targeted solutions tosolve specificIT challenges Workloads Resources


Consolidation PlanningWhat is It?

Planning the move from this (physical)… …to this (virtual)


Consolidation PlanningHow 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


Consolidation PlanningOne-time vs. Continuous

• One-time• Aggressive• Try to virtualize as much as

possible at once• Goal – maximum cost saving• One-time project• Low upfront cost

(sometimes free)• Risks

– Hardware can’t support the number of servers virtualized

– Hardware can’t support the type of workloads virtualized

• Continuous• Conservative• Multiple rounds of virtualization,

select “lowest hanging fruit”• Goal – successful technology

adoption (IT and end-users)• Persistent software

(plan when you walk with the latest information)

• Software has a cost


How Virtualization Changes Requests for Resources

Before Virtualization After Virtualization

I need 3 servers to run

this application.


How Virtualization Changes Hardware Purchases

$20k - purchased to meet the needs of a user

Before Virtualization

$200k - purchased to meet the needs of all users

After Virtualization


What is Virtualization Capacity Management?

Awareness of Available Resources

Opportunitiesfor Reclamation

Identificationof Bottlenecks

Configuration Issues

Cost Saving/Avoidance

VirtualizationCapacity

Management


Virtualization Capacity ManagementAwareness of Available Resources

What we want What we have


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


Demo

Use PlateSpin® Recon to analyze a 'critical

SUSE® 11 Server' workload to determine if

it is a candidate for virtualization.

PlateSpin® Migrate


PlateSpin® Migrate

Physical Servers Virtual HostServer Workloads

Data

Applications

Operating System

Migrate Windows and Linux workloads into a VMware, Microsoft Hyper-V or Xen virtual environment

Test new workload to ensure it runs as predicted with no impact to production server

Sync over changes that occurred during the test cycle and put new workload live

1 2 3


Virtualization Steps

1 InitialWorkloadCopy

3 ServerSync

4 Cutover

2 Test andVerify

App. Users

App. TestTeamApp. Users

App. Users


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 testing2. Validate the results obtained during the assessment and

planning stage3. Minimize cutover outage if an offline cutover is needed


Staged Transfer With Images

Source Site Target Site

1

Requirements

• Site to site interconnect• Large Bandwidth• Small Used Disk Space (<50 GB)


Direct Transfer (Peer-to-peer)


1

Requirements


2Classic File TransferSAN ReplicationRemovable Media

3


Staged Transfer With Images and Server Sync


1

Requirements


2Classic File TransferSAN ReplicationRemovable Media

3

4


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


Server Sync: Optimized Testing

Test your virtualized environment with minimal downtime

With PlateSpin

Without PlateSpin®

Migrate

Test

Cut Over

Migrate

Test & Validate

Cut Over


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


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


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


Cost Savings

Scheduling functionality helps minimize costs for staffing during off-hoursE-mail notifications removes the tether during the migration process – no need to sit and watch the progress barOptimized File-transfer reduces the duration of migrationsSimplified testing reduces downtime for your workloads reducing costs associated with a server outage

Reduces overall costs of all types of migration projects


Demo

Based on previous consolidation assessment, set up

migration as well, show how you would set up a server

sync once 'testing' is complete.

Consolidated Disaster Recovery – P2V DR via PlateSpin® Protect


Leveraging Virtual Infrastructure to Protect Physical Servers

Physical Production Servers

Virtual Recovery Hosts

Physical Production Servers


PlateSpin® Protect and Forge

Secondary EnvironmentProduction Server

Replicate servers (physical or virtual) into a secondary virtual environment

IT admin tests workloads in new environment to ensure they run as expected

Production server goes down, power up virtual machines in secondary environment in minutes

Secondary Environment


Users

Production Server(Offline)

1

2

3Production Server

Users


PlateSpin® Protect

Image library

Replicate servers (physical or virtual) into an image library

Replicate incremental changes on a daily, weekly or monthly basis

Production server goes down, deploy image to new or existing hardware over the network

Recovery Server Image library

1

2

3

Production Server

Users

Image libraryProduction Server

Users


Consolidated Disaster RecoveryBenefits

• 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



Consolidated Disaster RecoveryHow Does It Work?

Production Server

Step 1:Replicate servers (physical or virtual) into a secondary consolidated virtual environment

Step 2:Test workload in new environment to ensure it runs as predicted

Step 4:Restore/recover workload to new or existing hardware in minutes

Production Server

Recovery Server




Step 3:Production server goes down, the workload can run in a virtual environment until new hardware is provisioned, thus reducing downtime


Where Do We Fit?

Solution Cost RPO RTO TTO

Server Clustering $$$$$$ Near Zero Near ZeroNear Zero(Impacts production data)

PlateSpinConsolidatedRecovery

$$$$ Minutes MinutesMinutes(No impact to production data)

Image Capture $$$ 24h HoursHours (Requires additional hardware)

Tape/Manual Rebuild $ 24h+ Days Days

(Not practical)


Novell Identity Manager

Novell Access Manager

Novell Roles Based Provisioning Module

Novell Access Governance Suite

Novell Privileged User Manager

Novell SecureLogin®

Novell Cloud Security Service

How Novell® Delivers Intelligent Workload Management

Build Secure Manage MeasureSUSE® Linux Enterprise Server

SUSE Studio

SUSE Linux Enterprise JeOS

Novell® ZENworks® Configuration Management

SUSE Appliance Toolkit

Novell Workshop

Novell Business Service Manager

Novell Business Service Level Manager™

Novell Business Experience Manager™

Novell myCMDB™

Novell Sentinel™

Novell Sentinel Log Manager

Novell Compliance Automation Solution

* Available by end of 2010

PlateSpin® Orchestrate

Novell ZENworks Configuration Management

PlateSpin Migrate

PlateSpin Recon

PlateSpin Protect

PlateSpin “Atlantic”

PlateSpin “BlueStar”

Novell Definitive Software Library

* Covered in VWM 100

Questions...

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 DisclaimerThis 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.

Date post:	18-Nov-2014
Category:	Documents
Upload:	novell
View:	2,458 times
Download:	1 times

Virtualizing Mission-critical Workloads: The PlateSpin Story

Documents